The Design of Everyday Things

You push a door, but it needs to be pulled. A sign explains this – yet many people make the same mistake. “People don't read” is the quick response. Don Norman asks the more uncomfortable question: why does the design suggest the wrong action?

The Design of Everyday Things shows that usability problems often arise from the relationship between person and system. Good design makes possibilities, consequences and the current state understandable instead of merely assuming correct behaviour.

1. Make possible actions and signals readable

An object or interface offers certain possibilities for action. Signals – Norman calls them “signifiers” – indicate where and how to act: a visible recessed handle, a clearly labelled button or a highlight. When the signal contradicts the actual function, uncertainty follows.

People form a mental model from this: an idea of how the system works. Good design supports an appropriate model. It does not require users to understand the internal technology, but makes relationships consistent enough to predict behaviour.

2. Design mapping, constraints and feedback

Natural mapping connects a control and its effect understandably – for example, when four switches mirror the spatial arrangement of four hobs. Constraints prevent impossible or dangerous actions before an error message is needed.

Each action needs appropriate feedback: was it saved? Is the process still running? What can happen next? Feedback should be prompt and informative. A moving circle without information may signal activity but leaves unclear whether progress is being made or something is stuck.

3. Investigate the system rather than blaming the person

Norman distinguishes different kinds of human error. A slip of the tongue or accidental click despite a correct intention needs different countermeasures from a deliberate action based on a mistaken understanding. Blanket appeals for more attention therefore do little good.

Recurring errors are valuable observations. They reveal where design creates false expectations, hides important information or prevents safe correction. Human-centred innovation starts with observing and testing – not with assuming the designer already knows every user's perspective.

Your exercise: redesign a stumbling point

Choose an object, form or digital process where people frequently hesitate:

1. Minute 1 – observe. Which action do users expect, and which visible signal creates that expectation?
2. Minute 2 – cause. Is an understandable mapping, a constraint, feedback or an appropriate mental model missing?
3. Minute 3 – prototype. Sketch one change and decide which real person you would test it with.

In the test, check not whether the person understands your explanation, but whether they recognise the next step without additional explanation.

What we take from this

Norman's principles connect empathy with systematic design. In WEITER7 , an observed stumbling point becomes a concrete development area: name the assumption, build a small change, observe use and iterate.

Which recurring “user error” have I explained as inattention – and what might it reveal about the design?

Context: This insight summarises selected principles from Norman's work in our own words. The example, exercise and WEITER7 connection are our own adaptations. Good usability depends on context, abilities and user diversity; one brief test does not replace accessible, participatory and professionally sound evaluation. Not every error can be prevented by interface design alone.

Sources and further reading: Don Norman's official book page ↗ · Nielsen Norman Group: Book overview ↗