Distance between a control and its object decides whether the mapping can be inferred

What it is

On a lighting console, a dimmer sitting next to the lamp it drives is used without anyone reading the legend — the hand goes to the lamp. Move those same dimmers to a panel across the room and the engraved names are unchanged, yet the causal link has to be guessed again. Control-object proximity is what makes “this acts on that” readable from layout.

The two ends are not peers. One issues a command; the other is rewritten. The distance is answering which object this control moves, not merely which items look grouped.

Why it happens

People read an interface as a diagram. Spatial correspondence is treated as control correspondence: stove knobs that mirror the burner layout are almost never pressed wrong; knobs in a line against burners in a square produce immediate errors. That pathway is faster than reading, and labels struggle to override it — labels are the slow channel that opens after the spatial hypothesis fails.

Once the two ends no longer share a visual group — unrelated controls, a divider, another column in between — the grouping cue is gone. People probe, or they hunt for text. Probing is most expensive when the action cannot be undone.

Studying it

Stimulus-response compatibility tasks keep the same control-object pairs and compare spatially compatible versus incompatible layouts on reaction time and error. The stove-knob population stereotype questionnaire belongs here too: no labels, only positions, “which burner does this knob drive?”

Independent variables: relative placement of control and object, number of intervening distractors, presence of labels. Dependent variables: mapping accuracy, whether the first attempt hits the intended object, hesitation before confirming.

A more interface-native variant: cover every label and ask people to point at the object of each control. That exposes whether distance is carrying the mapping, better than a satisfaction score.

Where it stops holding

The effect is strongest on one-to-one panels whose spatial structure is stable — mixers, lighting, multi-camera rigs. In lists whose membership changes every visit, positional correspondence is itself unstable and inference collapses. Keyboard, shortcut, and screen-reader users never take this visual mapping. When the object is an invisible scope (“the whole document”, “whatever has focus”), there is nothing to sit next to. Lab compatibility advantages come from repetitive, low-semantics keying; on a settings page opened twice a year, people may read the labels first and the spatial effect shrinks.

Applying it

• Put the control in the object’s own block: image tools against the canvas, not the window chrome; row actions inside the row, not in a page-level footer.
• Do not insert unrelated controls on the mapping path; they split the visual group.
• For one-to-one hardware-like arrays (multi-gang switches, camera tiles), make the spatial topology isomorphic with the object topology. Alphabetical order will tear the mapping apart.
• How to check: blank every label and icon glyph on a screenshot, then ask someone new to the UI “which region does this control change?” Each wrong point is a mapping the layout failed to state.

Related

• Same group: F1.01.2 Distant mappings need an explicit pointer or highlight · F1.01.3 When one control acts on many objects, the scope must be marked
• Nearby: F1.03 Proximity and saccades · F2.06 Proximity grouping
• Search terms: control-object proximity · spatial mapping · stimulus-response compatibility