mapping

• SKILL.mdcore · 10,190 bytes
• references/lineage.mddoc · 7,319 bytes

# Mapping

> **Definition.** Mapping is the relationship between a control and the effect it produces. Good mapping makes the connection immediately apparent — by spatial position, shape, motion, or convention — so the user does not have to think, label, or memorize. Bad mapping requires the user to translate between control and effect, which is slow, error-prone, and quietly punishing.

The classic test of mapping is the four-burner stove. Four knobs in a row, four burners in a 2×2 grid. Which knob controls which burner? In a poorly mapped stove the answer requires labels (and, even with labels, half a second of squinting); in a well-mapped stove the knobs are arranged in a 2×2 grid that matches the burner layout, and you simply reach for the knob in the position of the burner you want.

The same problem appears in software a hundred times a day. The arrow keys move the cursor in the direction of the arrow — strong mapping. The "swap" button has two arrows curving in opposite directions — strong mapping. The "settings" gear icon has no inherent connection to settings — weak mapping, sustained only by convention. The number "3" next to a column header increases the column count by 3 — questionable mapping; better would be a stepper that visibly changes the column layout in real time.

## Why this matters

The cost of weak mapping is paid every single time the user reaches for a control. A user of a four-burner stove with bad mapping turns on the wrong burner perhaps once a month — usually when distracted, sometimes when something is on the burner and shouldn't be heated. This is the core observation that Don Norman built *The Design of Everyday Things* around: most "user error" is actually a design failure to make the mapping obvious. The user is not confused because they are stupid; the user is confused because the designer asked them to memorize an arbitrary pairing in a context where the cost of getting it wrong is real.

In digital interfaces, the punishment is subtler but constant. Every weak mapping costs a few hundred milliseconds of cognitive lookup ("which one was the save icon again?"), and a percentage of the time it costs an actual error: clicking the delete button when you meant to click archive, swiping the wrong way to dismiss, hitting the wrong toggle in a settings panel because the labels and the affected setting are not visually linked. These costs are paid millions of times across a product's user base, and they compound especially in high-stakes flows (cockpit controls, medical devices, financial transactions, legal forms) where a single mismapped action can be expensive or dangerous.