Loading…
Loading…
The relationship between controls and their effects, making interactions feel intuitive.
stellae.design
Mapping, as defined by Don Norman, is the relationship between controls and the things they affect. Good mapping leverages spatial correspondence — the arrangement of controls corresponds to the arrangement of outcomes. The best mapping is 'natural mapping,' where the relationship is obvious without instruction. In digital design, mapping applies to how interface controls relate to content manipulation, navigation, and system behavior.
Mapping, as defined by Don Norman, describes the relationship between controls and their effects in the world. Good mapping means the layout and behavior of controls correspond naturally to the outcomes they produce, making systems intuitive without instruction. Poor mapping forces users to memorize arbitrary relationships, increasing errors, slowing task completion, and generating frustration that compounds with every interaction.
A cooktop arranges its four control knobs in the same spatial layout as the four burners they control — top-left knob maps to top-left burner. Users never need to read labels because the physical mapping makes the relationship self-evident. This is Norman's classic example of natural mapping eliminating the need for instruction.
A design application lets users drag objects on a canvas and see them move in real-time under the cursor. Resizing happens by pulling handles at the exact corners of the object, and rotation follows the angular movement of the drag. The mapping between gesture and outcome is so direct that the interface disappears from consciousness.
A smart home app lists controls for lights, thermostat, locks, and music in a single alphabetical column with no spatial or categorical grouping. The living room light switch sits between the kitchen lock and the master bedroom thermostat. Users must read every label carefully because the arrangement provides no mapping cues to the physical environment.
• The most common mapping error is arranging controls by system logic — alphabetical order, database ID, or implementation convenience — rather than by the spatial or conceptual relationships users expect. Another frequent mistake is inverting natural directions, such as scroll bars that move content opposite to the drag direction or volume sliders that decrease when pulled right. Teams also underestimate the power of grouping: even when perfect spatial mapping is not feasible, clustering related controls together provides partial mapping that dramatically reduces errors.
Was this article helpful?