The Design of Everyday Things

Why products fail, affordances, signifiers

Norman opens with a deceptively simple question: why do we struggle with everyday objects like doors, stoves, and light switches? The answer lies in poor design that ignores human psychology. He introduces the concept of affordances — the properties of an object that suggest how it can be used. A flat plate on a door affords pushing; a handle affords pulling. When the affordance matches the intended action, interaction is intuitive.

Signifiers are signals that communicate where action should take place. While affordances are properties of objects, signifiers are communicative devices — arrows, labels, sounds, or visual cues that guide behavior. A well-designed product uses signifiers to make affordances discoverable. A poorly designed product hides or contradicts its affordances, creating the "Norman door" phenomenon where you push when you should pull.

The conceptual model — the user's mental understanding of how something works — determines whether interaction succeeds or fails. Good design ensures the system image (what the product communicates through its appearance and behavior) aligns with the designer's conceptual model. When there's a mismatch, users construct incorrect mental models and blame themselves for errors that are actually design failures.

Feedback — information about what action has been performed and what result has been accomplished — is essential for usable design. Every action should produce an immediate, informative, and perceptible response. Missing feedback leaves users uncertain whether their action registered. Excessive feedback overwhelms. The challenge is calibrating feedback to be noticed without being annoying.

• Affordances suggest possible actions; signifiers communicate where to act
• Mental models determine whether users understand a product
• Good feedback is immediate, informative, and proportional
• Most "user errors" are actually design errors

• Photograph 5 poorly designed objects and identify the affordance/signifier mismatch
• Redesign a confusing interface using Norman's principles
• Observe someone using an unfamiliar app and note where they struggle — map it to Norman's concepts

• Blaming users for design failures
• Adding features without considering discoverability
• Providing too much or too little feedback
• Designing for the ideal user rather than the actual user

Gulf of execution and evaluation, seven stages of action

Norman presents his Seven Stages of Action model, a framework for understanding how people interact with the world: (1) Goal — form the intention, (2) Plan — determine the sequence of actions, (3) Specify — translate the plan into specific actions, (4) Perform — execute the actions, (5) Perceive — observe the state of the world, (6) Interpret — make sense of what happened, (7) Compare — evaluate whether the goal was achieved.

The Gulf of Execution is the gap between what the user wants to do and the actions available. If a user wants to bold text but cannot find the bold button, the gulf is wide. The Gulf of Evaluation is the gap between the system's state and the user's understanding. If the system has applied the bold formatting but the display doesn't change visibly, the gulf of evaluation is wide. Good design minimizes both gulfs.

Learned helplessness occurs when people repeatedly fail with technology and internalize the belief that they are incompetent. Norman argues this is almost always a design failure, not a personal failing. Designers must take responsibility for making products that people of all technical abilities can use successfully.

• Seven Stages of Action provides a diagnostic framework for interaction problems
• Gulf of Execution and Gulf of Evaluation are the two fundamental design challenges
• Learned helplessness with technology reflects design failures, not user incompetence

Memory, mapping, natural constraints

Humans combine knowledge in the head (learned, memorized information) with knowledge in the world (external cues, labels, mappings) to navigate complex systems. Good design puts information in the world so users don't need to memorize procedures. A well-labeled control panel requires no training; a blank panel requires extensive memorization.

Natural mappings exploit spatial correspondence between controls and their effects. The best mappings are physical — a stove where burner controls are arranged in the same layout as the burners themselves. Cultural mappings rely on conventions — moving a slider right increases the value. Good mappings feel obvious; bad mappings require thought.

Constraints limit possible actions, guiding users toward correct behavior. Physical constraints prevent physically impossible actions (a USB-C plug only fits one way). Semantic constraints rely on meaning (a car seat faces forward). Cultural constraints depend on conventions (red means stop). Logical constraints use reasoning (only one remaining option must be correct).

• Good design puts knowledge in the world rather than requiring memorization
• Natural mappings create intuitive correspondence between controls and effects
• Four types of constraints guide correct behavior: physical, semantic, cultural, logical

Physical, cultural, semantic constraints

This chapter deepens the exploration of constraints and conventions. Norman demonstrates how well-designed products make the correct action the easiest action through a combination of constraints, affordances, and mappings. LEGO bricks exemplify brilliant constraint design — the studs physically prevent incorrect assembly while making correct assembly satisfying.

Forcing functions are a special type of constraint that prevent errors by requiring a specific sequence of actions. A microwave that won't start with the door open, a car that won't shift out of park without pressing the brake, and a document that requires saving before closing are all forcing functions that prevent potentially dangerous mistakes.

• Well-designed constraints make correct actions easy and errors difficult
• Forcing functions prevent dangerous mistakes through required action sequences
• The best designs make the right thing to do obvious without instructions

Slips vs mistakes, designing for error

Norman distinguishes two fundamental types of human error: slips (the goal is correct but the action is wrong — pressing the wrong button, pouring orange juice into your coffee) and mistakes (the goal itself is wrong due to incorrect understanding). Slips occur with practiced actions when attention wanders. Mistakes occur with novel situations where the user's mental model is flawed.

Design for error follows several principles: make it easy to discover and correct errors (undo, confirmation dialogs), make it hard to perform irreversible actions (requiring multiple steps for deletion), make it easy to reverse actions (undo stacks), and change the attitude toward errors (treat them as expected rather than exceptional). The Swiss cheese model of accidents shows that catastrophic failures result from multiple small errors aligning — good design adds barriers at every level.

Root cause analysis, borrowed from industrial safety, reveals that most "human error" is actually systemic failure. Blaming the operator obscures the design flaws, training deficiencies, and organizational pressures that created the conditions for error. This insight has transformed industries from aviation (crew resource management) to healthcare (surgical checklists).

• Slips = right goal, wrong action; Mistakes = wrong goal entirely
• Design should anticipate, accommodate, and recover from errors
• Root cause analysis reveals systemic failures behind individual errors
• The Swiss cheese model shows how multiple small failures combine into disasters

HCD process, iteration, prototyping

Design thinking is a human-centered, iterative approach to solving problems. The process follows four activities: observation (understanding people's actual needs through ethnographic research), ideation (generating multiple creative solutions without premature judgment), prototyping (building rough versions to test ideas quickly), and testing (observing real users with prototypes to identify problems).

The double diamond model describes two phases: Discover and Define (understand the right problem to solve) and Develop and Deliver (find the right solution). Many design failures occur because teams jump to solutions without properly understanding the problem. Norman emphasizes that the most important design skill is asking the right question, not generating clever answers.

Prototyping ranges from low-fidelity (paper sketches, wireframes, cardboard models) to high-fidelity (interactive prototypes, 3D prints). The key insight is that prototypes are tools for thinking, not demonstrations of solutions. Early prototypes should be deliberately rough to encourage feedback — polished prototypes make reviewers reluctant to suggest changes.

• Human-centered design follows observe → ideate → prototype → test cycles
• Understanding the problem is more important than generating solutions
• Low-fidelity prototypes encourage more honest feedback than polished ones
• Design thinking is applicable far beyond product design — to services, organizations, and policies

Competing constraints, feature creep, innovation

Real-world design must balance competing constraints: business requirements (cost, schedule, market positioning), technical constraints (what's feasible), and human needs (usability, desirability, accessibility). The designer's role is to navigate these tensions, not to satisfy one dimension at the expense of others.

Feature creep — the relentless addition of features to products — degrades usability over time. Each individual feature may seem reasonable, but their cumulative effect overwhelms users. Norman advocates for activity-centered design, where features are organized around natural workflows rather than listed in menus. The iPod's scroll wheel succeeded because it was designed for the activity of browsing a music library.

Incremental innovation (improving existing products) and radical innovation (creating entirely new categories) require different design approaches. Most companies focus on incremental innovation because it's predictable and lower risk. Radical innovation — the telephone, the smartphone, the GPS — requires technology push combined with deep understanding of latent human needs.

• Design navigates business, technical, and human constraints simultaneously
• Feature creep is the enemy of usability — organize features around activities
• Incremental and radical innovation require different design strategies