Mode Error¶
The interaction failure in which the same user action is interpreted differently by a system depending on a hidden mode the user does not perceive — the user acts correctly for the mode they believe is active, and the system, in the actually active mode, does something else.
Core Idea¶
A mode error is the HCI failure in which the same physical action is interpreted differently depending on a hidden mode the user does not currently perceive: the user performs the action correct in the mode they believe is active, and the system, in the actually active mode, does something else. Its structure has three parts — a mode-overloaded action space, a weak or peripheral mode indicator, and a hidden or unobserved transition — so the user's believed mode and the system's actual mode diverge unregistered. It is a design failure, not user carelessness.
Scope of Application¶
Lives across HCI, aviation human factors, medical-device design, and control-room engineering, wherever a control surface interprets a gesture mode-relative and the active mode can go unperceived.
- Text editors and modal interfaces — vi insert-versus-command confusion.
- Aviation autopilot and autothrottle — Sarter and Woods's FLCH/V·S/VNAV mode confusion.
- Ventilators and infusion pumps — SIMV/PRVC/AC modes; bolus-versus-continuous.
- CNC machinery and industrial controls — setup-versus-run-versus-maintenance modes.
- Automotive controls — electronic shifters (the Jeep recall) and drive-mode selectors.
Clarity¶
Naming mode error rescues a class of incidents from the "user error" verdict, relocating the fault from operator inattention to an interpretive mapping that changed without announcing itself — which redirects the remedy from "train harder" to design change. It also slots into the error taxonomy, distinguishing a slip (motor stumble), a mistake (flawed goal cleanly executed), and a mode error (right goal, clean execution, silently shifted interpretation).
Manages Complexity¶
A wide spread of incidents otherwise arrives under one undifferentiated "user error" verdict that names no cause and licenses only more training. Mode error compresses it to three conditions that hold or not, collapsing the diagnosis to one comparison — did believed and actual mode diverge, and was the indicator strong enough to catch it? — and handing the designer three matching levers, one per condition.
Abstract Reasoning¶
The three conditions and the attribution flip license diagnostic inference (correct intent plus clean execution plus a wrong result is the mode-error signature, distinct from slip and mistake), interventionist design (each lever aimed at one condition; training predicted to fail), boundary-drawing (design fault versus operator deficit; route each error type to its lever), and predictive reasoning (errors concentrate under workload and out-of-view displays; cost scales with what the wrong-mode action controls).
Knowledge Transfer¶
Within HCI, aviation, medical devices, and control rooms the concept transfers as mechanism — the three conditions, the attribution flip, the taxonomy, and the one-lever-per-condition defences presuppose only a mode-relative control surface. Beyond it the state-relative-interpretation pattern recurs as co-instances (a status-dependent legal act, a culture-dependent gesture, a protocol-state packet), carried by the parents contextual_mode_switching, frame_of_reference, state_machine, and error_proofing_poka_yoke — the mode-indicator machinery stays home.
Relationships to Other Abstractions¶
Current abstraction Mode Error Domain-specific
Parents (2) — more general patterns this builds on
-
Mode Error presupposes Contextual Mode Switching Prime
A mode error presupposes a system that switches among discrete context-selected mappings before the user's believed mode can diverge from the active one.
-
Mode Error is part of Mental Model Prime
Mode error contains the operator's internal model of the active mode whose prediction is correct for the believed state but mismatched to the system's actual state.
Hierarchy paths (3) — routes to 3 parentless roots
- Mode Error → Contextual Mode Switching → Adaptation
- Mode Error → Mental Model → Representation → Abstraction
- Mode Error → Contextual Mode Switching → State and State Transition → Phase Space
Neighborhood in Abstraction Space¶
Mode Error sits in a sparse region of the domain-specific corpus (76th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Interface Legibility & Navigability (12 abstractions)
Nearest neighbors
- Microcopy Ambiguity — 0.83
- Orientation Loss — 0.83
- Operable Design — 0.83
- Keyboard Accessibility — 0.82
- Keyboard Trap — 0.82
Computed from structural-signature embeddings · 2026-07-12