Don Norman and The Design of Everyday Things
Featuring Don Norman
Every time you push a door that should be pulled, or spend thirty seconds fighting a hotel faucet, you are living inside a design failure. Don Norman, the cognitive scientist who joined Apple in the 1990s and co-founded the Nielsen Norman Group, spent a career explaining why it is never your fault. His 1988 book handed the field a vocabulary it still uses, and one example became so common it earned its own name: a door that gives you the wrong signal, so you push when you should pull and feel vaguely stupid for it.
For anyone building a product, this is a case about the moment a user makes a mistake and quietly blames themselves. It sharpens a simple audit: when people get it wrong, was the cue clear, did anything tell them what to do, did the action confirm it worked? The framework Norman built to separate bad users from bad design, and how to run it against your own most common support ticket, is the part the app holds back.
Frequently asked questions
What is The Design of Everyday Things by Don Norman about?
It is Don Norman's 1988 book arguing that when people struggle with everyday objects, the fault lies with bad design, not the user. Norman, a cognitive scientist who later joined Apple and co-founded the Nielsen Norman Group, gave the field a lasting vocabulary including affordances, signifiers, and feedback.
What is a Norman door?
A Norman door is a door that gives you the wrong signal, so you push when you should pull and feel vaguely stupid for it. It became such a common example from Norman's work that it earned his name, illustrating how a missing or misleading cue causes the user to make a mistake.
Why do people blame themselves when a design fails?
Norman's point is that users instinctively blame themselves the moment they make a mistake, even though the real problem is usually that the design gave a poor cue, no signal of what to do, or no confirmation that an action worked. Pushing a pull door or fighting a hotel faucet is a design failure, not a personal one.
What can product and design teams learn from Don Norman's work?
Run a simple audit on the moments users get something wrong: was the cue clear, did anything tell them what to do, and did the action confirm it worked? Reframing user error as a design signal points you straight at what to fix. CaseBook turns this into a move you apply to your own product, with an AI coach that reads your answer.