Business 1988
The Design of Everyday Things
《设计心理学》
- Published
- 1988
- Category
- Business
- Difficulty
- Beginner
- Reading time
- ~8 hours
- Original language
- en
The Classic Index is not an objective scientific measure. It is this site's personal curation score.
What is this book about?
Norman explains why everyday objects confuse us, arguing that the blame usually belongs to design rather than to users, and introduces concepts such as affordances, signifiers, mapping, and feedback. That vocabulary is now standard in discussions of usability.
Why read it?
It changed how designers think about human error, and its core insight — that errors are usually system failures — generalizes far beyond product design. It is also unusually clear writing about cognition.
Core Ideas
- When people struggle with a device, the fault usually lies in its design, not in their intelligence.
- Good design makes the correct action obvious through affordances and signifiers.
- Errors are predictable and can be designed for, and slips should be distinguished from mistakes.
- Understanding how the mind works is a prerequisite for designing well.
What questions does this book try to answer?
- Why are everyday objects so confusing?
- How do you design systems that make serious errors less likely?
Who should read it?
For designers, product managers, and engineers. No psychology background is needed; the examples are ones everyone has lived through.
Reading Notes
2026-10-07
When the same mistake is made by one person after another, the defect is usually not in the people but in a design that failed to make the right action obvious.
The key move in this book is to shift "making a mistake" out of the moral register and into the register of design. Norman's central claim is that when an everyday object requires a manual to be used correctly, the defect lies in the affordances it offers rather than in the competence of its user — people are not irrational, they are following the cues the design supplies. What it genuinely changes is the direction of attribution: recurring operational errors get diagnosed as properties of a system rather than as individual carelessness. The caution worth keeping is that the same lens can be abused; assigning all responsibility to "design" and "the system" gradually erodes the capacity to own a consequence. The easily missed point is that Norman does not argue for eliminating error at all. He argues for making error visible, reversible, and cheap — a far more realistic goal than zero defects, and a more honest one in engineering terms.
Related Books
If you like this book
