THE READING ROOM / BOOK GUIDE
The Design of Everyday Things
A cognitive scientist examines why doors, switches and interfaces frustrate us, and argues that the fault usually lies in the design rather than the user.
About the book
Don Norman's book looks at the ordinary objects people handle every day and asks why so many of them demand instructions, apologies or guesswork. A door that needs a sign telling you to push is, in his terms, a failure of design. The book builds a vocabulary for that failure and for its opposite: affordances that suggest use, feedback that confirms action, and mappings that let controls match what they operate.
Norman writes as a cognitive scientist who spent years studying how people perceive and act, then turned that lens on manufactured things. His central argument is that human error is often a mislabel. When a person pulls a door that should be pushed, the design invited the mistake. He develops this through examples drawn from kitchens, offices, vehicles and early computer interfaces, using them to show how mental models and visible structure guide behavior.
The book helped establish user-centered design as a mainstream concern and remains a reference point for anyone thinking about how products meet people. Its concerns reach beyond industrial design into software, architecture and any setting where someone has to figure out how a thing works.
How to read it
Read it as an argument built from cases rather than a manual. Norman returns to the same handful of examples, so pay attention to how each one is used to isolate a principle. The prose is plain and the chapters move briskly, though some passages assume comfort with psychological terms such as affordance and mapping.
The examples date from the late 1980s, so expect references to telephones, doors and early computers rather than smartphones. That distance is useful: the principles survive even where the objects have changed. Keep a pencil nearby to test his claims against devices you own, and notice where a modern interface confirms or complicates his account.
Who it suits
Designers, engineers and product managers will find a shared language for problems they already sense but struggle to name. Students entering human-computer interaction or industrial design get a compact foundation. General readers who have ever felt stupid in front of a microwave or a ticket machine will recognize the frustration and come away with a sharper eye for why it happens.
Reading considerations
The book is a product of its period, and its examples can feel dated to readers expecting contemporary digital case studies. Some later editions add material, so check which version you have before relying on page references. Norman's confidence that better design can resolve most friction is worth testing against situations where cost, regulation or competing users constrain the solution.
Follow the HN conversation
Read riwsky’s original comment (2020-09-05) ↗
Search HN comments about this book ↗
Explore videos on the same subject ↗
Book notes prepared with DeepSeek, using catalogue records and Open Library subject information. They are reading guidance, not a personal review or a verified chapter-by-chapter account. Book details can vary by edition. HN data methodology · Book metadata and covers.
