The Design of Everyday Things

Summary

Key takeaways

1. 1.

   When a user fails to operate something correctly, the first question should be whether the design failed them, not whether they failed the design. Most errors are design problems in disguise.

2. 2.

   Affordances are the properties of an object that suggest how it can be used. A good handle tells you where to grab it. A well-designed button tells you it can be pressed.

3. 3.

   Signifiers make affordances perceivable. Good design communicates possibilities and constraints without requiring the user to read a manual.

4. 4.

   Conceptual models are the mental images users build of how a system works. The more closely the system's actual behavior matches those models, the easier it is to use.

5. 5.

   Feedback tells the user what just happened. Without feedback, errors compound invisibly. Good design responds immediately and clearly to every user action.

6. 6.

   Norman distinguishes slips (right intention, wrong execution) from mistakes (wrong intention). They call for different design responses — slips call for better controls, mistakes call for better information.

7. 7.

   Forcing functions and constraints are design's safety net. They make wrong actions physically impossible or highly inconvenient, rather than relying on the user to remember not to make them.

8. 8.

   The emotional dimension of design matters. An object that delights its user will be used more, tolerated more, and repaired rather than discarded. Aesthetics and usability are not in conflict.

Discussion questions

Use these on your own, with a book club, or as chat starters in Superbook.

1. 1.

   Norman argues that blaming the user for errors is almost always wrong. Think of a recent time you were frustrated by a product. Was the problem your error or a design failure?

2. 2.

   Pick one object in the room you're in. What affordances does it communicate? Does it have any false affordances — things that suggest it can do something it can't?

3. 3.

   Norman writes about 'doors that look like they should push but actually pull.' Where does your workplace or home have the equivalent of that design failure?

4. 4.

   How does the idea of conceptual models help explain the difficulty of learning new software? What conceptual model did you arrive with that turned out to be wrong?

5. 5.

   The book distinguishes slips from mistakes. In your own work, which kind of error do you make more often? How does the environment you work in help or hinder you?

6. 6.

   Norman updates the 1988 edition for the digital age. Where do you see the affordances framework applying — or breaking down — in app or software interfaces you use regularly?

7. 7.

   Feedback is one of Norman's key principles. Think of a digital interface that gives you good feedback versus one that gives you almost none. What's the difference in your experience of using them?

8. 8.

   Norman suggests that good design feels obvious in retrospect but is actually very hard to achieve. Can you think of a product that achieves this? What makes it work?

9. 9.

   The book's constraints chapter discusses physical, cultural, semantic, and logical constraints. Which type of constraint do you rely on most in the systems you use?

10. 10.

    Norman's framework is about everyday objects as much as digital interfaces. How does thinking about affordances and signifiers change how you look at physical objects in your environment?

11. 11.

    If you had to redesign one thing in your home or workplace using Norman's principles, what would you choose, and what would you change?

Themes

Frequently asked questions

• What is The Design of Everyday Things about?

  It argues that most design that frustrates users is the designer's fault, not the user's. Norman uses concepts from cognitive psychology — affordances, signifiers, feedback, and mental models — to explain what makes something easy or hard to use, and how to do it right.

• Is the 1988 edition or the 2013 revision better?

  The 2013 revision is generally preferable. Norman updated examples to include digital interfaces and software, added material on emotional design, and corrected some terminology. The original introduced the term 'affordances' in a way that confused the field; the revision clarifies it.

• Is The Design of Everyday Things only for designers?

  No. It's most often assigned in design programs, but it's useful for anyone who builds products, writes software, manages processes, or creates systems that other people use. Engineers and product managers often find it as useful as designers.

• What's the most memorable concept in the book?

  The Norman door — a door that looks like it should push when it should pull. It's become a piece of design vocabulary for any interface that sends the wrong signal about how it works. Once you know the term, you spot Norman doors everywhere.

• Does the book hold up after forty years?

  The core framework holds up well. Some examples feel dated, and the digital chapters of the 2013 edition are already showing their age relative to current AI and voice interfaces. But the underlying principles about human cognition and error haven't changed.

About Donald Norman

Donald Norman is a cognitive scientist and design theorist who served as vice president of Advanced Technology at Apple and later co-founded the Nielsen Norman Group, one of the leading UX research consultancies. He taught at the University of California San Diego and held visiting positions at Harvard and other institutions. Originally a cognitive psychologist, Norman's work brought human factors and cognitive science into mainstream product design. The Design of Everyday Things, first published in 1988 and revised in 2013, is the most widely assigned text in design education and a foundational document of the human-centered design movement.