the design of everyday things

If you have ever shoved a door marked 'pull,' cursed a stove, or failed to program a VCR, this book hands you relief and a toolkit. It turns everyday frustration into a diagnosable design failure and gives principles — visibility, mapping, feedback, constraints — you can apply to anything you make or buy. Essential for designers, engineers, product managers, and anyone who wants to stop blaming themselves for bad objects.

1. 1Chapter 2

   The projector meltdown that started it all

   Norman is at a conference in Italy, watching the next speaker attempt to thread a film onto a projector he has never used. The speaker puts the reel in place, takes it off, reverses it. Another person comes to help, then two more, then another. Voices rise in three languages — Italian, German, English — as someone pokes at the controls and announces each result. Confusion mounts until the organizer turns to the audience and asks if anybody is expert in projectors. Fourteen minutes after the speaker started to thread the film, a blue-coated technician appears, scowls, takes the entire film off the projector, rethreads it, and gets it working.

   The idea

   Norman didn't laugh this scene off; he used it as a lab. Threading a projector should be simple, so he asked what makes any action hard, and the answer became the structure of action that runs through the whole book. The surprise is that a mundane, slightly comic failure can reveal the anatomy of every human action — and that the fault sits in the object's design, not the crowd of intelligent adults it defeated.

   Try this: Next time you fumble with a device in public, note exactly which step confused you — that step is a design bug worth naming.

2. 2Chapter 2

   Seven stages: how every action actually happens

   A person reads in an armchair as dusk falls and the page dims. The goal is to get more light, translated into an intention to switch on a lamp, which requires specifying how to move the body, stretch to reach the switch, and extend a finger to push the button. Nothing happens until the action is executed on the world. Then evaluation runs in reverse: the person perceives the world (the light is on), interprets whether the light is actually on according to expectations, and compares the outcome to the intention and goal (is there enough light to read?).

   The idea

   Every action, from dim lamps to film projectors, follows the same loop: form a goal, form an intention, specify an action, execute, then perceive, interpret, and evaluate. Designers who know the loop can pinpoint exactly where an object fails — does it hide what to do, or hide what happened? The seven stages double as a checklist for bridging both gaps, which is why this framework became the book's spine.

   Try this: Pick one task that annoyed you today and trace it through all seven stages to find the broken link.

3. 3Chapter 2

   Two gulfs between you and your machine

   Back at that Italian conference, the projector failed in two distinct ways. First, a long, complex sequence was required instead of a simple setup, making it unclear what actions had to be done. Second, even when the film was in the projector, it was difficult to tell if it had been threaded correctly, so the user could not easily evaluate the state of the system. Norman names these the gulf of execution and the gulf of evaluation, and shows the same double failure in a VCR: the user sees the solution as simply pressing the Record button, but the required actions include pressing record, specifying the time through multiple steps, selecting the channel, and saving the settings.

   The idea

   The gulf of execution is the gap between what you want and what the device allows; the gulf of evaluation is the effort of figuring out what the device is doing. As Norman puts it, 'The gulf is small when the system provides information about its state in a form that is easy to get, is easy to interpret, and matches the way the person thinks of the system.' Good design shrinks both gulfs at once — and most bad gadgets fail one of them.

   Try this: Audit one app you use: list the steps between your goal and the result, and delete one.

4. 4Chapter 1

   Doors that lie: affordances and signifiers

   Norman opens the book with the objects you touch without thinking. A door affords pushing or pulling — those are the possible interactions between an object and its user, a concept he borrows from the ecological psychologist James J. Gibson. The trouble starts when the door gives no signal about which action it wants. A flat plate on a door signals 'push,' while a long rounded bar or handle signals 'pull'; a small finger-size push-button signals press here. Doors with ambiguous affordances cause people to push when they should pull, and everyone standing behind them suffers.

   The idea

   An affordance is what an object makes possible; a signifier is what tells you about it. The distinction matters because possibility without a visible signal is useless — a door that affords pulling but looks pushable will be pushed. Once you see signifiers, you can't stop noticing how many objects stay silent exactly when you need instructions.

   Try this: Find one door in your building that confuses people and sketch what signifier would fix it.

5. 5Chapter 1

   Stop blaming yourself

   Norman notices a pattern in how people fail with everyday objects: when something seems to malfunction, they apologize. They assume they pressed the wrong button, misunderstood the manual, or lack some technical gift. He flips the verdict — it is not the fault of the user but the lack of intuitive guidance in the design. Design, he argues, is communication between object and user, and the job is to optimize that channel so using things becomes pleasurable rather than humiliating.

   The idea

   This reframe is the book's emotional core. Learned helplessness around technology isn't a personal defect; it's evidence that the object failed to communicate. Once you accept that bad design causes 'user error,' you stop feeling stupid and start asking better questions: what signal was missing, what mapping was wrong? That shift in blame is what makes the rest of the book's principles feel like justice rather than technique.

   Try this: The next time you fumble a device, write down what the design could have signaled to prevent it.

6. 6Chapter 3

   Knowledge in the head and in the world

   Norman discusses how knowledge can be distributed between what is in the head (memory) and what is in the world (environmental cues), using the example of a telephone keypad, where the layout is in the world, but the number to dial is in the head. The division is deliberate and useful: memory is precious and error-prone, so good design pushes arbitrary information out into the environment where you can see it instead of recalling it. Designers who demand memorization are spending the user's mental budget on trivia.

   The idea

   Knowledge doesn't have to be stored in one place. Precise, arbitrary details — a phone number, a sequence of steps — belong in the world; your head should hold the gist. The surprise is how much of 'intelligence' is actually good environmental cueing. When an interface forces you to memorize what it could easily display, it is taxing your memory for no reason, and errors follow.

   Try this: Move one piece of information you keep re-memorizing — a password, a bin schedule — into the world where you can see it.

7. 7Chapter 4

   Constraints: making the wrong action impossible

   Norman introduces the concept of constraints, including physical constraints (such as a key that only fits into a lock in one orientation) and uses the example of Lego blocks, which can only be assembled in certain ways due to their physical shape. He sorts this guidance into four kinds: physical, semantic, cultural, and logical constraints.

   The idea

   Constraints get a bad reputation as restrictions, but Norman treats them as a gift: the fewer wrong actions available, the fewer errors you can make. A well-constrained task teaches itself, because the object's shape and context eliminate the manual. The insight generalizes beyond objects — workflows, forms, and software all improve when the design makes the wrong path physically or logically unavailable rather than merely discouraged.

   Try this: Redesign one recurring mistake in your routine so the wrong option is physically harder than the right one.

8. 8Chapter 5

   Slips and mistakes: two different failures

   Norman splits human error into two species. A slip is when the intention is right but the execution goes wrong — you mean one action and perform another. A mistake is deeper: the intention itself is wrong because the wrong goal was chosen. The distinction changes the remedy, because a slip needs better feedback and guards on execution, while a mistake needs a better understanding of the situation itself.

   The idea

   Most error analysis collapses these two, then applies the wrong fix. If you treat a mistake as a slip, you add confirmations that annoy skilled users; if you treat a slip as a mistake, you retrain people who only needed a guard. Norman's taxonomy gives designers a diagnosis before a prescription — and it explains why 'be more careful' never fixed anything.

   Try this: Next time you err, classify it: right goal, wrong move, or wrong goal entirely?

9. 9Chapter 5

   Design for error, because errors will come

   Norman accepts a hard truth: users will make errors no matter how good the instructions are. So the design should anticipate them — minimize the consequences, make actions easy to reverse with something like an undo function, make irreversible errors hard to commit, and give clear feedback so people can detect and correct problems before damage spreads.

   The idea

   Designing for error inverts the usual posture of blame. Instead of asking users to be perfect, it assumes imperfection and builds a safety net. The undo function is the canonical case: it converts a catastrophe into a non-event. Systems that punish every slip teach users to fear them; systems that forgive errors keep users exploring, which is where competence actually comes from.

   Try this: Add an 'undo' path to one destructive action in your own work — a draft, a delete, a send.

10. 10Chapter 6

    User-centered design: the user, not the designer

    Norman popularizes the term user-centered design (also called human-centered design), describing it as design based on the needs and capabilities of the user, not the preferences of the designer, leaving aside secondary issues like aesthetics. In practice it means simplifying the structure of tasks, making things visible, getting the mapping right, exploiting the powers of constraint, designing for error, explaining affordances, and applying the seven stages of action.

    The idea

    The radical move is whose judgment counts. Designers know their creations too well, so they can't feel the confusion a first-time user feels; only the user's needs and capabilities can anchor decisions. Aesthetics isn't banned, just subordinated — beauty that obscures function is a defect. The checklist nature of the method is its strength: you don't need genius, you need discipline.

    Try this: Hand your latest creation to someone uninitiated and watch in silence where they hesitate.

11. 11Chapter 6

    The four principles of good design

    Norman outlines principles of good design: visibility (the user can tell the state of the device and the alternatives for action — the correct parts must be visible and convey the correct message). A good conceptual model is one of the principles of good design. Good mappings between controls and effects (such as stove knobs arranged in the same pattern as the burners). Feedback about the results of actions (immediate and continuous information, since a lack of feedback leads to frustration).

    The idea

    These four principles are derived from the seven stages of action. The stove-knob example shows good mappings between controls and effects. Objects that follow these principles feel obvious; objects that violate them feel like they were designed to spite you.

    Try this: Check your kitchen stove: do the knobs map to the burners, or is it guesswork every time?

12. 12Chapter 7

    The design challenge: everyone wants a say

    In Chapter 7, Norman discusses the tension between the needs of different stakeholders in design. Design is a tug-of-war among stakeholders, such as engineers, marketers, and users, and the designer must balance aesthetics, manufacturability, cost, safety, and usability, often under constraints that make user-centered design hard to achieve. The principles are simple; the politics of making them win is not.

    The idea

    Norman's honesty about competing requirements turns the book from a lecture into a strategy guide: if you care about users, you must learn to argue for them in the meetings where trade-offs get decided.

    Try this: In your next product debate, voice the user's requirement out loud as a stakeholder with equal standing.

13. 13Preface to the 2002 edition

    A title change and a peace treaty with designers

    In the preface to the 2002 edition, Norman recounts that a group of industrial designers felt affronted after reading an early draft of the book, so he rewrote it to be more sympathetic to the design profession. In the preface to the 2002 edition, Norman explains that although his academic peers liked the original title, The Psychology of Everyday Things, he changed it to The Design of Everyday Things because the new title better conveyed the book's content and attracted interested readers.

    The idea

    Even a book about clear communication had to redesign itself. It's a fitting coda from a man who insists designers, not users, bear the blame.

    Try this: Rename one thing you made — a file, a project, a team — to match what your audience actually calls it.

Designers, engineers, and product managers who ship things other people must use — and anyone who has ever felt stupid fighting a door, a stove, or a remote. It converts daily frustration into a fixable design problem.

FAQ