The Design of Everyday Things Summary

Norman introduces affordances and signifiers as key to good design. An affordance is an object's property that suggests how it can be used—a flat surface suggests pushing, a handle suggests grasping. However, not all affordances are visible. This is where signifiers come in: they are clear cues or signals that show where an action should happen or what options exist. A well-designed object uses both, making its function clear without instructions. When these are mismatched or missing, users become confused and frustrated, showing the designer's failure to communicate the intended interaction. Understanding this difference is vital for creating intuitive, user-friendly products that require little mental effort.

People interact with the world by forming mental models of how things work. These models come from experience, instructions, and perceived affordances and signifiers. A designer's job is to ensure that the 'design model' (how the designer intends the product to work) closely matches the 'user's model' (how the user understands it) and is well-represented by the 'system image' (what the user sees and interacts with). When these models differ, users get confused, make mistakes, and blame themselves, leading to frustration. Good design provides a clear, consistent, and accurate system image that helps users form an effective mental model, letting them predict outcomes and use the device confidently.

Mapping refers to how controls relate to their effects. Good mapping means the relationship is natural and clear, allowing users to intuitively understand which control does what. The best mappings are based on spatial analogy (e.g., moving a joystick left moves an object left), cultural conventions (e.g., red for stop, green for go), or direct visual match. Poor mapping, where controls are arranged illogically or have no clear connection to their function, forces users to memorize arbitrary links. This causes errors and frustration, especially in complex control panels where a lack of natural mapping can make simple tasks feel overwhelming.

Feedback is the information a system gives the user about their actions. It confirms an action has been registered, shows progress, or signals an error. Effective feedback must be immediate, clear, and informative, letting users know if their action was successful and the system's current state. Without feedback, users are left guessing, leading to uncertainty, repeated actions, and a feeling of being out of control. Lack of feedback often causes frustration, making users wonder if the system is working or if their input was received. Good feedback reassures users and helps them correct mistakes.

Constraints are limits that guide users towards correct actions and prevent errors. Norman identifies several types: physical (e.g., a plug only fits one way), semantic (e.g., a large object cannot fit into a small hole), cultural (e.g., standard road signs), and logical (e.g., knowing all parts must be used in an assembly). By cleverly applying constraints, designers can reduce the number of choices a user considers, making the task simpler and less prone to error. Good constraints do not feel restrictive; instead, they make the correct action feel natural and the incorrect action impossible or unlikely. This improves usability and safety. They are a proactive way to prevent errors.

Norman challenges the idea of 'human error.' He argues that what is often called a user mistake is actually a design failure. When a product is hard to use, confusing, or misleading, the design has failed to suit human thinking, perception, and behavior. Users are often blamed, which leads to frustration and inadequacy. The real problem is a design that lacks clear affordances, has poor mapping, insufficient feedback, or an inconsistent mental model. By shifting blame from the user to the design, Norman empowers designers to take responsibility and inspires a more empathetic approach to product creation. The focus becomes making things 'discoverable' and 'understandable,' rather than assuming user incompetence.

Discoverability means whether it is possible to figure out what actions are possible and how to perform them. Understanding, on the other hand, is about how the product should be used and what all controls and settings mean. A truly well-designed product achieves both: its functions are immediately clear (discoverable), and its operation is intuitive and logical (understandable). When a product lacks discoverability, users cannot interact with it effectively. When it lacks understanding, users might struggle without grasping the underlying logic. Designers must integrate affordances, signifiers, constraints, mapping, and feedback to ensure both aspects are strong, making the product a pleasure, not a puzzle, to use.

Norman highlights the 'paradox of technology,' where advancements, while promising more functionality and ease, often add new complexity. Early versions of new technologies are often clunky, hard to use, and require significant user effort to master. This initial complexity comes from the newness of the concepts, the lack of established design conventions, and the many features packed into new devices. Only through repeated refinement, user feedback, and a deep understanding of human psychology does technology become truly simple, intuitive, and seamlessly integrated into daily life. Designers must be aware of this paradox and aim to reduce initial mental effort, even as they push technological boundaries.

Norman breaks down human interaction with systems into a 'Seven Stages of Action' model, covering goal formation, execution, and evaluation. These stages are: forming the goal, forming the intention, specifying the action, executing the action, perceiving the state of the world, interpreting the state of the world, and evaluating the outcome. This framework shows that user interaction is a cyclical, goal-driven process. Designers can use this model to find potential problems or failures in their products. By ensuring clear communication, feedback, and intuitive controls at each stage, designers can make user journeys smooth, minimize mental effort, and help users achieve their goals efficiently. It is a powerful tool for finding design weaknesses.

Instead of designing for perfect users, Norman suggests designing with the certainty of human error in mind. People make mistakes—slips (unintentional errors) and lapses (memory failures) are part of being human. Good design anticipates these errors and either prevents them (using constraints, clear mapping) or makes them easy to detect, recover from, and minimize their impact (through clear feedback, undo functions, confirmation dialogues). A forgiving design ensures that errors are not catastrophic and that users can easily get back on track without frustration or significant loss. This approach shifts the design philosophy from expecting perfect users to creating robust systems that handle imperfect human interaction gracefully.