Design Principles
Norman: Mapping
The relationship between a control and its effect should be natural and obvious.
Where it comes from
It's another of Don Norman's design principles. His classic example is the stovetop: burners arranged in a square but controls in a row leave you guessing which knob works which burner — a failure of mapping between control and effect.
Why it matters for your website
Controls should map naturally to their effects. Norman's principle of mapping says the relationship between a control and what it does should be intuitive — the layout, direction, and grouping all matching the user's expectation. Poor mapping forces trial and error, which on the web means hesitation and mistakes.
Good mapping uses spatial and conventional correspondence so the right control is obvious. When a control's position, direction, or grouping mirrors the thing it affects, the user knows what it does without thinking; when the relationship is arbitrary, they're reduced to trial and error.
On the web this shows up in sliders that move the wrong way, controls placed far from what they change, and groupings that imply relationships that don't exist. Each forces a small experiment, and experiments on a page the user can leave are a risk.
Wrong vs right
A set of controls placed far from the elements they affect, so it's unclear which control changes what.
Each control placed next to, or clearly mapped to, the thing it controls, so the relationship is obvious.
A volume or brightness slider where dragging up decreases the value, contradicting expectation.
Directional controls that follow convention — up for more, right for forward — matching the user's mental model.
A row of identical switches with no spatial correspondence to the items they toggle.
Switches arranged to mirror the layout of what they control, so the mapping reads at a glance.
Understanding Norman: Mapping
Norman's principle of mapping concerns the relationship between a control and its effect: the more natural and obvious that relationship, the more usable the control. Good mapping exploits spatial correspondence and established convention so that the user can tell what a control does from its position, direction, or grouping, without having to experiment.
His famous illustration is the stovetop, where burners in a square and knobs in a line force you to learn, or guess, which controls which. The same problem recurs on screen: a slider that moves counter to expectation, a control placed nowhere near what it changes, or a grouping that suggests a relationship that isn't real. Each breaks the intuitive link between action and result.
Where mapping is poor, users fall back on trial and error — and on the web, that means hesitation, mistakes, and a sense that the interface is fighting them. Strong mapping makes a control's effect predictable before it's even used, which is what lets people act with confidence. It connects to affordances, the law of proximity, and self-evident design.
How Kweri checks it
Mapping is partly observable and partly a matter of convention and judgement. Kweri can flag some likely mapping problems — controls placed far from what they affect, or groupings that may imply the wrong relationships — but whether a control's behaviour matches user expectation often only emerges in use. So Kweri surfaces spatial and grouping cues that may be sending the wrong signal about what controls what, and prompts you to check the mapping, while confirming it feels natural is a matter of testing with real users.
FAQ
What is mapping in design?
Mapping is the relationship between a control and its effect. Good mapping makes that relationship natural and obvious — through position, direction, or grouping — so users can tell what a control does without trial and error. It's one of Don Norman's core principles.
What's an example of good and bad mapping?
Norman's classic bad example is a stovetop with burners in a square but knobs in a row, leaving you guessing. Good mapping places knobs to mirror the burners, so each control's effect is obvious. Online, controls placed beside what they change map well.
Why does poor mapping hurt usability?
Because it forces users to experiment to learn what each control does. On the web, that trial and error means hesitation and mistakes, and an interface that feels unpredictable — undermining the confidence users need to act.
How do I create good mapping?
Use spatial correspondence and convention: place controls near or arranged like the things they affect, follow directional expectations (up for more, right for forward), and group controls to reflect real relationships. The effect of a control should be predictable before it's used.
Who developed the principle of mapping?
Don Norman, as one of the core design principles in The Design of Everyday Things. It's part of his broader framework for making everyday objects and interfaces intuitive.
Related principles
Speak the user's language — use familiar words and conventions, not internal jargon.
Users arrive with expectations from past experience — break those without reason and you cause confusion.
Good design externalises the knowledge users need to act — it puts it in the world, not in their heads. A product that requires memorisation is a product that requires training.
Attribution & sources
Identified by Don Norman. Catalogued from The Design of Everyday Things (Don Norman).
One of Norman's core design principles; there's no single canonical web source.
See Norman: Mapping on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →