Mode ambiguity needs its own lamp or legend, not reliance on remembering the current mode

What it is

“The user will remember whether this is navigation or radio” is not mitigation; it stores the mode in working memory. An independent mode indicator is a lamp that is not the key’s own print, a persistent function name, a swappable cap—something whose job is to answer “what is this control now.” That is not the same as a factory legend wearing off the cap: the legend states the as-tooled meaning; the indicator states the current meaning.

Why it happens

Working memory will not hold a mode name across minutes, especially when a primary task is full. The indicator must sit beside the control, be readable in periphery, and last for the whole time the mode lasts—not flash at the switch. Independence from the cap matters because the cap must remain a tactile landmark; changing how it feels every mode would dismantle homing. Lamp codes must stay few: two modes as two colors or on/off; three and more start needing a legend. If the indicator still requires a lookup table (red means pinch-zoom?), the memory burden has only moved house. The best indicator puts the current function’s word next to the key, not a color code that has to be learned.

Studying it

Compare no indicator, a switch animation, a persistent lamp, and adjacent text, on capture under distraction and eyes-free use.

Independent variables: indicator type and whether it persists, distance from the control, color versus text coding, ambient light. Dependent measures: capture rate, time to find the current function name, whether a color code is understood.

Bright sun, polarized lenses, and color vision deficiency are required conditions for the indicator channel, not corners. An animation that has ended before the action joins “no indicator.” Asking “do you remember the mode” measures memory, not the indicator.

Where it stops holding

A one-key-one-meaning panel needs no mode indicator. Lamps fail, and they go dark in power-save; if the system still shift-works when they are dark, people are sent back to memory. A night-bright indicator can interfere with driving or photography; brightness must follow ambient. Many keys each on shift-work, each with a lamp, become a Christmas tree and the code collapses—cut the shift-work rather than add lamps. Worn legends and language revisions belong to the next group; this layer only requires that current meaning have an independent, living representation.

Applying it

• Every physical control on shift-work gets a persistent current meaning beside it: words before color codes; lamps only when there are two states.
• When the indicator is dark, lock shift-work to the default function, or refuse to execute the non-default meaning.
• Do not replace a persistent indicator with a one-shot animation or a first-run tutorial.
• Verify: without first asking the mode name, have people under distraction press that key to do the current job. Capture with no indicator versus persistent text is the indicator’s contribution. The indicator must remain readable in sun, night, and a color-vision simulation. Turn the indicator off and confirm that non-default functions are blocked.

Related

• Same group: C10.13.1 One physical control doing different jobs in different modes is a mode effect in hardware form · C10.13.2 After a mode switch the control usually looks the same, so people keep the previous mode’s expectations · C10.13.3 When frequent and infrequent functions share a control, mis-operation cost should bias toward making the infrequent function safer
• Adjacent: C10.14 Labels and Illumination of Physical Controls · C10.07 Tradeoffs Between Physical and On-Screen Controls
• Search: mode indicator · mode lamp · externalized mode