Don Norman’s central claim is deceptively simple: when you push a door that was meant to be pulled, or can’t find the light switch, that is not your stupidity, it is a design failure. The book takes the everyday frustrations we blame on ourselves and reframes them as evidence that most objects are built without regard for the psychology of the people using them, then lays out the principles that fix it.
The fault is in the design, not the person
Norman came to design through catastrophe. His background is in the study of human error in aviation and nuclear accidents, and the pattern he kept finding was that “human error” was almost always the last link in a chain that started with a bad design: controls that looked identical, feedback that never arrived, mappings that invited the wrong action under pressure. The moral generalises all the way down to the light switch and the stove. If a system regularly produces the same mistake across many different people, the problem is not the people, it is the system, and blaming the user is both unkind and useless because it fixes nothing. This reframing is the spine of the whole book: design is a moral act because it decides in advance who gets to succeed and who gets made to feel stupid.
Affordances, discoverability, and the Norman door
An affordance is the relationship between an object and a user: a flat plate affords pushing, a handle affords pulling and grasping. Good design makes the right actions perceptible and the wrong ones invisible, so the object tells you how to use it without a manual or a sign. The failure case became so iconic it is now literally called a “Norman door”: a door with a handle you instinctively pull, that actually needs to be pushed, betrayed by a “PUSH” sticker that is a confession the design already failed. A sign taped onto an object is a design smell; if you need instructions for a door, the door is broken. (In the 2013 revision Norman split this idea, reserving “affordance” for what actions are possible and coining “signifier” for the perceivable signal that tells you where to act, because a possible action that no one can perceive is useless.)
Knowledge in the head versus knowledge in the world
We navigate the world far more successfully than our memories should allow, and Norman’s explanation is that we offload most of the work onto the environment. We do not memorise which of a hundred coins is real; we recognise it when we see it, because the knowledge lives “in the world,” not “in the head.” Good design deliberately puts knowledge into the world through visible options, natural constraints, and mappings, so behaviour can be driven by recognition rather than recall. The tradeoff is real and he names it: knowledge in the world is easy to use but clutters the environment and disappears when the object isn’t present, while knowledge in the head is fast and portable but expensive to learn and easy to forget. The designer’s job is to strike the balance, leaning on the world for the things people do rarely and letting expertise move into the head for the things they do constantly.
The seven stages of action and the two gulfs
To explain why some things are hard to use, Norman dissects what happens when you do anything at all. An action runs through seven stages: forming a goal, then an intention, then a plan of action, executing it, then perceiving the world, interpreting that perception, and finally evaluating it against the goal. Two of these stages are where designs fail, and he names the failures as gulfs. The Gulf of Execution is the gap between what you want to do and what the system lets you do: the movie-projector that takes fourteen minutes to thread because nothing about it suggests the correct sequence. The Gulf of Evaluation is the gap between the state the system is in and your ability to perceive and understand that state: you acted, but the machine gives no feedback, so you cannot tell whether it worked. Two design tools bridge these gulfs: a good conceptual model (so you can plan the right action) and immediate, visible feedback (so you can tell what happened), and almost every “confusing” device is confusing because one of these is missing.
Two kinds of error: slips and mistakes
Norman insists that “human error” is not one thing. A slip is when you have the right intention but the execution goes wrong: you pour orange juice into your coffee, or drive to the office on your day off out of habit. A mistake is when the intention itself is wrong: you formed the wrong goal or plan, often because your conceptual model of the situation was flawed. The two need different design responses, but the meta-point is that errors are normal and predictable, so good design assumes they will happen and contains them. The remedies are concrete: forcing functions that make the dangerous action physically impossible (a microwave that won’t run with the door open), constraints that only permit correct assembly, confirmation for irreversible acts, and above all easy undo so that an error is a nuisance rather than a disaster.
Norman’s design toolkit
Stripped to its parts, the book is a small, durable checklist for whether a design will work. Provide a good conceptual model, so the user’s mental picture matches how the thing actually behaves. Make the relevant parts and options visible, so possibilities are discoverable rather than hidden. Use natural mappings, where the layout of controls mirrors the layout of what they affect (the classic failure being four stove knobs in a row controlling four burners in a square). Give full and continuous feedback, so every action produces a perceptible result. Exploit affordances and constraints, so the object suggests correct use and resists incorrect use. None of these are about beauty; they are about making the machine explain itself.
Lessons worth keeping
- When many people make the same error, redesign the system, do not retrain the people. Blame located in the user is a design failure in disguise.
- A sign or an instruction bolted onto an object is an admission that the design failed. Aim for things that need neither.
- Bridge the two gulfs deliberately: give people a conceptual model good enough to plan the right action, and feedback fast enough to know whether it worked.
- Design for error, not against it. Assume slips and mistakes will happen and make them cheap: forcing functions, constraints, confirmation on the irreversible, and always undo.
- Push knowledge into the world for the rare and the dangerous; let it live in the head only for what people do constantly.
- Natural mappings beat labels. If you have to label which control does what, the mapping is already wrong.
Related
- meaghan-choi-designing-claude-code - a modern designer applying the same “make the mental model visible” instinct to AI tooling.
- build-ai-that-earns-user-trust - feedback, predictability, and conceptual models as the basis of trust in AI products.