Mapping is the relationship between a control and its effect. Good mapping makes it obvious which control does what, without labels or trial and error.
Overview
Mapping describes how well controls correspond to the things they affect. The classic example is a kitchen stove: when the knobs are arranged in the same layout as the burners, people pick the right knob instantly. When four knobs sit in a straight row beneath a square of burners, people hesitate, guess, or need labels.[1]
Norman calls the ideal natural mapping: using spatial layout, physical analogy, or cultural convention so the relationship is understood immediately. Moving a control up should make something go up or increase. A control placed next to an item should act on that item.[1][2]
In digital products, mapping shows up in where actions are placed relative to the content they affect, the direction of sliders and scrolling, the order of steps in a form, and whether the structure of the interface matches the way people think about their work.
Why it matters
Poor mapping causes slow, error-prone interactions even when everything is technically labeled. People apply an action to the wrong record, adjust the wrong setting, or have to stop and think about which control does what. Each instance is small; across thousands of users and transactions the cost is significant.
Research dating back to the 1950s shows that when controls are arranged to match the things they control, people respond faster and make far fewer errors.[3][4]
Key takeaways
- Put controls near what they affect. Actions for a row belong on or beside that row; actions for a whole table belong above the table.
- Match spatial layout. When controls represent things with a physical or visual arrangement, mirror that arrangement.
- Follow expected direction. Up, right, and clockwise usually mean more or forward in left-to-right cultures; respect platform conventions for scrolling and sliders.
- Mirror the real-world process. Order form fields and workflow steps the way people actually perform the task, not the way the database stores the data.
- Mappings are cultural. Reading direction, date formats, and color meanings vary. In some markets red signals a rise in value rather than a loss. Global products should test mappings with global audiences.
- When natural mapping is not possible, label clearly. Labels are a fallback, not a substitute for a good arrangement.
In practice
Common patterns in business applications, portals, and internal tools:
Supports the principle | Undermines the principle |
|---|---|
Edit and delete actions appear on the specific item they affect. | A single toolbar far from the list that acts on whichever item happens to be selected. |
Settings show a live preview of their effect next to the control. | Settings pages where the effect is only visible after saving and navigating elsewhere. |
Form sections follow the order of the real process (requester, details, approval). | Fields grouped by back-end table rather than by the user’s task. |
Bulk actions appear only once items are selected, directly above the selection. | Bulk actions mixed in with page-level actions, unclear about what they will affect. |
Layouts adapt correctly for right-to-left languages. | Hard-coded left-to-right assumptions in direction-dependent controls. |
Questions to ask in a design review
- Is it obvious which item or area each control will affect?
- Does the order of this screen match the order in which people actually do the work?
- Would a person from a different region or language interpret direction and color the same way?
- Could we remove a label because the arrangement already makes the relationship clear?
Origin
The study of mapping began in human-factors engineering. In 1953, Paul Fitts and Charles Seeger described stimulus-response compatibility: people respond faster and more accurately when controls correspond naturally to displays.[3][5] In 1959, Alphonse Chapanis and Lionel Lindenbaum tested four stove layouts and found that the arrangement whose controls clearly corresponded to the burners produced no errors at all, while the others produced many errors and slower responses.[4]
Don Norman popularized the term “natural mapping” in The Design of Everyday Things, using stoves, light switches, and car seat controls to show how much confusion disappears when layout carries meaning.[1]
Related concepts
- Law of Proximity — things close together are perceived as related
- Law of Common Region — elements within a shared boundary are seen as a group
- Fitts’ Law — distance to a target affects speed and accuracy
- Conceptual Model — mapping at the level of the whole system
- Constraints — limiting actions to the ones that make sense
- Jakob’s Law — familiar mappings carry over from other products
References and further reading
- Norman, D. A. (2013). The Design of Everyday Things: Revised and Expanded Edition. Basic Books. (Originally published 1988 as The Psychology of Everyday Things.) https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things
- Wikipedia. Natural Mapping (Interface Design). https://en.wikipedia.org/wiki/Natural_mapping_(interface_design)
- Fitts, P. M., and Seeger, C. M. (1953). S-R Compatibility: Spatial Characteristics of Stimulus and Response Codes. Journal of Experimental Psychology, 46(3). https://doi.org/10.1037/h0062827
- Chapanis, A., and Lindenbaum, L. E. (1959). A Reaction Time Study of Four Control-Display Linkages. Human Factors, 1(4). https://doi.org/10.1177/001872085900100401
- Wikipedia. Stimulus-Response Compatibility. https://en.wikipedia.org/wiki/Stimulus%E2%80%93response_compatibility
- Interaction Design Foundation. What is Mapping? https://www.interaction-design.org/literature/topics/mapping
- Yablonski, J. Laws of UX (format inspiration for this series). https://lawsofux.com/