BookBrief
The Design of Everyday Things cover
Archivist's Choice

The Design of Everyday Things

Donald A. Norman

Genre

Business / Psychology / Creativity / Technology / Science

Reading Time

240 min

Key Themes

See below

Track Your Reading

Sign in to track this book

Understand the hidden language of design in everyday objects, turning frustration into an appreciation for intuitive, human-centered creation.

Core Idea

Good design is invisible, intuitive, and human-centered. It makes everyday objects easy to understand and use by matching their perceived properties (signifiers and affordances) with their actual function. Bad design, however, causes frustration, errors, and a feeling of user incompetence. This happens when designers ignore basic psychological principles of human interaction, such as the need for clear feedback, effective mapping, and appropriate constraints. The book argues that many 'human errors' are, in fact, design errors. By understanding how people interact with the world, designers can create products that are not only functional but also pleasant and safe.
Reading time
240 min
Difficulty
Medium
✓ Read this if...
You are a designer, engineer, product manager, or anyone interested in understanding why some products are a joy to use and others are a constant source of frustration. This book is essential for anyone creating anything for human interaction.
✗ Skip this if...
You are looking for a highly technical deep-dive into specific design software or a purely aesthetic guide to visual design. This book focuses on the cognitive psychology behind usability, not graphic design.

Core idea

The central argument and framework that powers the entire book.

Good design is invisible, intuitive, and human-centered. It makes everyday objects easy to understand and use by matching their perceived properties (signifiers and affordances) with their actual function. Bad design, however, causes frustration, errors, and a feeling of user incompetence. This happens when designers ignore basic psychological principles of human interaction, such as the need for clear feedback, effective mapping, and appropriate constraints. The book argues that many 'human errors' are, in fact, design errors. By understanding how people interact with the world, designers can create products that are not only functional but also pleasant and safe.

At a glance

Reading time

240 min

Difficulty

Medium

Read this if...

You are a designer, engineer, product manager, or anyone interested in understanding why some products are a joy to use and others are a constant source of frustration. This book is essential for anyone creating anything for human interaction.

Skip this if...

You are looking for a highly technical deep-dive into specific design software or a purely aesthetic guide to visual design. This book focuses on the cognitive psychology behind usability, not graphic design.

Key Takeaways

1

Affordances and Signifiers

How objects communicate their use through inherent properties and explicit cues.

Quote

Affordances provide strong clues to the operations of things. Plates are for pushing. Knobs are for turning. Slots are for inserting things into. When affordances are taken advantage of, the user knows what to do just by looking: no picture, label, or instruction needed.

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 ...

Supporting evidence

Norman often uses the example of a door: a flat plate affords pushing, while a bar or handle affords pulling. Many doors are poorly designed, with pull handles on push doors, requiring explicit 'push' or 'pull' signs (signifiers) to correct the misleading affordance.

Apply this

When designing, identify the core actions users need to perform. Ensure the physical or digital interface inherently suggests these actions (affordances). If not immediately obvious, add clear signifiers (e.g., icons, labels, visual cues, contrasting colors) to guide the user without ambiguity. Test if users can intuitively understand how to interact with your design.

affordancessignifiersperceived-affordancesinteraction-design
2

The Power of Conceptual Models

Users build mental models; design should align with and reinforce them.

Quote

When the conceptual model is erroneous, people are apt to make mistakes. A good conceptual model allows us to predict the effects of our actions.

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 p...

Supporting evidence

Norman frequently discusses the complexity of VCRs (a common frustration point in his time) where the lack of a clear, consistent conceptual model for recording or programming led to widespread user difficulty. Another example is the 'desktop' metaphor in computing, which provided a strong conceptual model for file management.

Apply this

Before designing, understand your target users' existing mental models for similar tasks or objects. Design interfaces that leverage these existing models where appropriate, or clearly communicate new ones. Use consistent metaphors, terminology, and visual cues across your product to reinforce a coherent conceptual model. Test users' understanding of your product's underlying logic.

conceptual-modelsmental-modelssystem-imageuser-experience-design
3

Mapping and Natural Correspondence

Controls should naturally correspond to their effects for intuitive operation.

Quote

Mapping is a technical term, borrowed from mathematics, meaning the relationship between two things. In the design of everyday things, mapping is important in the relationships between controls and their effects.

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, ...

Supporting evidence

Norman details the confusing controls of a stovetop with four burners and four knobs, where the arrangement of the knobs doesn't match the arrangement of the burners, leading to constant errors. He contrasts this with car controls, where turning the steering wheel left makes the car go left, a natural and effective mapping.

Apply this

Whenever possible, arrange controls to spatially or perceptually correspond to the items they control. Use consistent color coding or grouping. For digital interfaces, ensure that dragging an item on screen moves it in the corresponding direction. If direct mapping isn't possible, use clear labels and proximity to group related controls and effects.

mappingnatural-mappingspatial-analogycontrol-design
4

Feedback: The Silent Communicator

Immediate and informative feedback is crucial for user confidence and error correction.

Quote

Feedback—sending back to the user information about what action has been done and what has been accomplished—is a well-known and powerful concept in control and information theory.

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....

Supporting evidence

Norman uses examples like the click of a button, the whir of a disk drive, or a loading bar on a computer screen. The lack of any indication when pressing a button, even if the action is registered, can lead users to press it multiple times, as seen with unresponsive elevator buttons.

Apply this

Design systems to provide immediate and unambiguous feedback for every user action, no matter how small. Use visual cues (e.g., highlights, animations, progress bars), auditory signals (e.g., clicks, beeps), or haptic feedback (e.g., vibrations). Ensure feedback is proportionate to the action and doesn't overwhelm the user, but is always present.

feedbacksystem-stateusabilityerror-prevention
5

Constraints: Guiding User Behavior

Limitations in design can prevent errors and simplify choices.

Quote

The power of constraints is to simplify the user’s mental task by restricting the possible actions at any given moment.

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 corr...

Supporting evidence

Physical constraints: only one way to insert a key into a lock. Logical constraints: a puzzle where all pieces must be used. Semantic constraints: a rider on a bicycle must straddle the seat, not sit on the handlebars. Cultural constraints: the accepted 'stop' sign shape and color.

Apply this

Actively identify opportunities to constrain user actions. Use physical design elements (e.g., different-sized ports, specific connectors) or digital interface elements (e.g., disabled buttons, dropdown menus, input validation) to prevent incorrect choices. Ensure constraints are clear and help, rather than hinder, the user's progress.

constraintserror-preventionphysical-constraintssemantic-constraints
6

The Root Cause of Human Error

Most 'human errors' are design errors, not user incompetence.

Quote

When we interact with things, we do not just interact with the physical device, we interact with its conceptual model. If the conceptual model leads us astray, then we make 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 resp...

Supporting evidence

Norman frequently cites examples like complex control panels in cockpits or medical equipment where operators, despite extensive training, make errors due to poor interface design, not a lack of skill or attention. He contrasts this with simple, intuitive designs where errors are rare.

Apply this

Adopt a 'blame the design, not the user' mindset. When users make mistakes, don't dismiss it as user error; instead, investigate how the design contributed to the error. Use error analysis as a critical tool for identifying design flaws and iteratively improving the product to prevent similar mistakes in the future. Design for the full range of human capabilities and limitations.

human-errordesign-failureuser-blameempathetic-design
7

Discoverability and Understanding

Good design makes functions obvious and how to operate them clear.

Quote

Discoverability results from the appropriate application of five fundamental psychological concepts: affordances, signifiers, constraints, mappings, and feedback. And understanding is how the product is to be used.

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 under...

Supporting evidence

Norman often critiques products with hidden functions or non-standard interfaces that require users to consult a manual. He praises designs where the very shape and layout of the object communicate its purpose and operation, like a well-designed pair of scissors or a simple light switch.

Apply this

Prioritize making all relevant functions and their operations easily discoverable. Use clear visual hierarchies, intuitive labeling, and consistent interaction patterns. After ensuring discoverability, focus on making the product's logic and purpose understandable through a coherent conceptual model. Conduct usability testing to observe if users can both find and comprehend how to use your product's features.

discoverabilityunderstandinglearnabilityuser-interface
8

The Paradox of Technology

New technology often adds complexity before it simplifies.

Quote

The greatest discoveries are not only those that solve problems but also those that uncover new ones. The paradox of technology is that it adds complexity before it can simplify.

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, int...

Supporting evidence

Norman points to the early days of personal computers, VCRs, and complex digital cameras. While these offered incredible power, their interfaces were often daunting, requiring users to learn entirely new paradigms and memorize obscure commands, highlighting the initial complexity before widespread adoption and design refinement.

Apply this

When introducing new technology, don't assume its inherent power will make it easy to use. Actively work to minimize complexity through thoughtful design, even if it means initially limiting features. Focus on making the core functionality incredibly simple and intuitive first, then gradually introduce advanced features. Prioritize user learnability and ease of adoption over sheer feature count.

technology-paradoxcomplexitysimplicityinnovation
9

Seven Stages of Action

Understanding human action helps designers support users through goal-oriented tasks.

Quote

Every action has two major parts: executing the action and evaluating the results.

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 communicati...

Supporting evidence

Norman applies this model to everyday tasks like making a cup of coffee or setting a thermostat. For example, if a user can't easily perceive the current temperature (perceiving the state), they can't effectively evaluate if their previous action (setting the thermostat) was successful.

Apply this

Map out your users' typical tasks using the Seven Stages of Action. For each stage, ask: 'Is it clear what the user's goal is?' 'Is it easy to form an intention?' 'Are actions obvious?' 'Is feedback clear?' 'Is the outcome easily interpretable?' Address any bottlenecks or ambiguities at each stage to optimize the user experience.

seven-stages-of-actiongoal-oriented-designcognitive-psychologytask-analysis
10

Design for Error, Not Perfection

Anticipate and accommodate human error through robust and forgiving design.

Quote

The greatest designs are those that are invisible, that don't call attention to themselves, that simply work.

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...

Supporting evidence

Norman discusses 'undo' functions in software, safety mechanisms in machinery (e.g., a car not starting if it's in gear), and confirmation prompts for destructive actions as examples of designing for error. He contrasts this with designs where a single misclick can delete hours of work without warning.

Apply this

Actively brainstorm potential errors users might make with your product. Implement design strategies to prevent these errors (e.g., constraints, default settings, clear labeling). For errors that cannot be prevented, design clear and immediate feedback, easy recovery paths (e.g., undo, cancel, clear error messages), and ensure that errors are not irreversible or destructive. Always test error handling with real users.

error-handlingforgiving-designrobust-designslips-and-lapses

Critical analysis

Notable Quotes

“Well-designed objects are easy to understand and use. They provide visible clues to their operation. The user knows what to do just by looking.”

— Introducing the core principles of good design.

“The problem is not in the human, but in the design. It is a demand for redesign.”

— Discussing how to approach user errors and design flaws.

“Affordances provide strong clues to the operations of things. Plates are for pushing. Knobs are for turning. Slots are for inserting things into.”

— Explaining the concept of affordances in design.

“When we have trouble with a device, we are quick to blame ourselves. 'I'm so stupid.' 'I can never get this to work.' This is the wrong conclusion.”

— Highlighting the psychological impact of poor design on users.

“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.”

— Reflecting on why good design often goes unnoticed.

“Constraints are powerful clues, limiting the set of possible actions. They allow us to determine the appropriate action even for novel situations.”

— Discussing the role of constraints in guiding user behavior.

“When an error does occur, it should be possible to undo the last action, or at least to make it clear what state the system is in.”

— Emphasizing the importance of error recovery and feedback.

“People make errors, which is why designs should tolerate them. When we make an error, we should be able to recover from it quickly and easily.”

— Advocating for designs that are forgiving of human error.

“Mapping is the relationship between the controls and their effects in the world.”

— Defining the concept of mapping in user interface design.

“The paradox of technology is that the same technology that simplifies life by providing more functions in each device also complicates life by making the device harder to learn, harder to use.”

— Addressing the inherent tension between functionality and usability.

“Feedback is critical. It must be immediate and informative.”

— Stressing the necessity of effective feedback in interactions.

“The most important things to design are the objects that people use every day.”

— Highlighting the significance of everyday objects in design.

“It is not enough that we build products that function, that are understandable and usable, we also must build products that bring joy and excitement, pleasure and fun, and yes, beauty to people's lives.”

— Expanding the scope of design beyond mere functionality to include emotional aspects.

Quiz

Test Your Knowledge

Ready to see how well you understood this book? Take our interactive quiz with 10 questions.

10
Questions
~5
Minutes
?
Best Score

Key Questions (FAQ)

This book explores the principles of good and bad design in everyday objects, explaining why some products are a joy to use while others are a constant source of frustration. It delves into the psychology behind human interaction with designed artifacts, advocating for user-centered design.

About the author

Donald A. Norman

Donald A. Norman

Donald A. Norman is a renowned cognitive scientist and usability engineer, best known for his seminal book 'The Design of Everyday Things.' His work emphasizes user-centered design and the psychology of how people interact with products and systems. Norman's influential ideas have shaped the fields of design, human-computer interaction, and cognitive psychology.