The Design of Everyday Things

The Book That Named the Problem

The Design of Everyday Things — originally published in 1988 as The Psychology of Everyday Things — introduced the vocabulary that designers and engineers have used for decades to discuss why products fail and what good design requires. Don Norman’s central argument is simple and has not dated: when people make errors with everyday things, the fault is almost always the design, not the user.

This inversion — from “the user did something wrong” to “the design failed to communicate” — is the book’s lasting contribution. It applies equally to light-switch panels, nuclear power plant controls, and smartphone interfaces.

Affordances and Signifiers

Norman introduced two concepts that have become foundational in design thinking. Affordances are the possibilities for action that an object offers a user — a chair affords sitting, a button affords pressing. Signifiers are the signals that communicate where and how those actions should be performed. The distinction matters because designers often confuse the two: an object can have excellent affordances but poor signifiers, resulting in users who have no idea how to use it correctly.

The classic example is the door with a flat push-plate on both sides — no way to know which side opens, or whether to push or pull. Norman calls these “Norman doors,” and once you know the term, you will never stop encountering them.

Feedback and Conceptual Models

Two more ideas complete the framework. Feedback is the communication back to the user that an action has occurred and what its result was. Conceptual models are the mental representations users build of how something works — often wrong in ways that produce systematic errors. Good design aligns the user’s conceptual model with the system’s actual behaviour. Bad design creates gaps between what users believe is happening and what is actually happening.

The Anatomy of Action and Error

Beyond its famous vocabulary, the book offers a rigorous model of how people actually use things. Norman breaks any interaction into seven stages of action — forming a goal, planning, specifying, executing, then perceiving, interpreting, and evaluating the result — and identifies two places where design fails: the “Gulf of Execution” (the user can’t figure out how to do what they want) and the “Gulf of Evaluation” (the user can’t tell whether it worked). He pairs this with a genuinely useful taxonomy of human error, distinguishing “slips” (you knew what to do but did it wrong) from “mistakes” (you formed the wrong intention in the first place), each requiring a different design remedy. The deep argument is humane and, in critical systems, lifesaving: rather than blaming and punishing people for inevitable errors, good design should make errors hard to commit and easy to recover from. Norman’s interest in this came partly from analyzing catastrophes like the Three Mile Island nuclear accident, where “operator error” turned out to be a story about terrible control-room design.

The Father of User Experience

It is hard to overstate this book’s influence on how the modern world is built. Don Norman is, quite literally, the person who coined the term “user experience” while at Apple in the 1990s, and the concepts he formalized here — affordances, signifiers, feedback, conceptual models, mapping, constraints — became the shared vocabulary of an entire profession. Every UX designer, product manager, and interaction designer working today is operating, knowingly or not, inside the framework Norman established. Through this book and his later work at the Nielsen Norman Group, he didn’t just describe human-centered design; he helped create the discipline. Reading it is, in a real sense, encountering the source code of how thoughtful products are conceived.

Strengths and Limits

The book’s revised 2013 edition wisely updated many examples to cover digital and mobile interfaces, keeping the argument current, but a few illustrations still feel rooted in an earlier era of stoves, telephones, and slide projectors. More substantively, The Design of Everyday Things is more analytical than prescriptive — it brilliantly diagnoses what good and bad design are, and trains your eye to spot them, but it offers less of a step-by-step method for actually producing great design, which readers must develop through practice and other resources. The depth of treatment also varies, with some chapters richer than others. None of this dims its core value; it simply means the book is a foundation to build on rather than a complete toolkit.

Final Verdict

The Design of Everyday Things is the rare book that permanently changes how you see the world. After reading it, you will never again struggle with a confusing door, a baffling stovetop, or an unintuitive app without instantly diagnosing exactly what the designer failed to communicate — and you will never again blame yourself first. Its central reframing, that “user error” is almost always design error, is one of the most quietly revolutionary ideas in modern technology, and the vocabulary it gave us — affordances, signifiers, feedback, conceptual models — underpins the entire field of user experience and the design of nearly every product you touch. Decades after its first publication, it remains the essential starting point for anyone who builds, designs, or simply uses the made world — and the rare professional classic that is also a genuine pleasure to read.

Our rating: 4.4/5 — Essential reading for anyone who builds, designs, or uses anything. Which is everyone.

Reading Guides

• Best Business Books of All Time: 23 That Every Leader Should Read (2026)
• 10 Best Productivity Books (Reviewed & Ranked by Experts)