The Design of Everyday Things
Don Norman · Interactive Chapter Guide
Book Guide

The Design of Everyday Things

Don Norman · 1988 (Revised 2013) · Basic Books
The foundational text of human-centred design. Norman reveals why everyday objects fail us — and whose fault it really is. Through affordances, signifiers, feedback, and conceptual models, he gives designers a vocabulary and a framework for creating objects that make sense without instructions.
AffordancesHuman-Centred DesignMental ModelsCognitive PsychologyProduct DesignUsability
Reference

Design Principles

7 core principles — click a card to filter linked chapters, click again to clear.

pan_tool
Affordances
Ch. 1 · p.1
An affordance is a relationship between an object's properties and a user's capabilities. A door handle affords pulling; a flat plate affords pushing. Bad affordances create bad interactions, regardless of labels.
UX: Buttons that look pressable, drag handles, visual depth cues
p. 1
label
Signifiers
Ch. 1 · p.1
Signifiers communicate where action should take place. Affordances exist in the world; signifiers communicate them. A "push" sign on a door is a signifier that compensates for a failed affordance.
UX: Labels on buttons, placeholder text, hover states, icons with labels
p. 1
model_training
Conceptual Models
Ch. 1 · p.1
The mental model users form about how a system works. When the designer's model matches the user's model, things work. When they diverge, errors and confusion result.
UX: Consistent metaphors, progressive disclosure, familiar UI patterns
p. 1
sensors
Feedback
Ch. 1 · p.1
Feedback communicates the result of an action. Without it, users don't know if they've been heard. Too much feedback is noise; too little creates anxiety. Good feedback is immediate, informative, and non-intrusive.
UX: Loading states, success messages, error states, micro-interactions
p. 1
tune
Mapping
Ch. 1 · p.1
Mapping is the relationship between controls and their effects. Natural mapping — where the spatial layout of controls mirrors the layout of the thing controlled — requires no labels and no learning.
UX: Stove burner layout, volume slider direction, scroll-to-zoom
p. 1
block
Constraints
Ch. 4 · p.109
Constraints limit the possible actions a user can take, guiding them toward correct behaviour. Physical constraints prevent mechanical misuse; logical constraints make incorrect paths visually obvious.
UX: Disabled states, form validation, SIM card orientation, forced flows
p. 109
report_problem
Human Error
Ch. 5 · p.147
Slips happen when the right goal leads to the wrong action (autocorrect gone wrong). Mistakes happen when the wrong goal is pursued. Both are design problems, not user problems. Design prevents both through forcing functions and reversibility.
UX: Undo, confirmation dialogs, irreversible-action warnings, poka-yoke
p. 147
Linked Chapters
FoundationsThe Psychopathology of Everyday Things

Norman opens with a devastating observation: we blame ourselves when objects fail us. Doors that push when they should pull, stoves where no burner corresponds to any control, software with 37 features nobody can find. These are not user failures — they are design failures. Understanding why requires dissecting the fundamental principles of good design.

01The Psychopathology of Everyday Things
Good design is invisible; bad design is felt as personal failure. Norman introduces the six fundamental design principles — affordances, signifiers, constraints, mappings, feedback, and conceptual models — that determine whether an object is usable without a manual.
affordancesignifiermappingfeedback
p. 1
02The Psychology of Everyday Actions
The seven stages of action: goal → plan → specify → perform → perceive → interpret → compare. Gulfs of execution and evaluation explain why users get stuck. Design must bridge both gulfs — communicating what can be done and what just happened.
seven stagesgulf of executionconceptual modelgoal
p. 37
Knowledge & ActionKnowing What to Do

The distinction between knowledge "in the head" and knowledge "in the world" is crucial. When design puts knowledge into the world — through labels, constraints, and affordances — users don't need to remember anything. When knowledge must be in the head, training and manuals become necessary. The best designs exploit both.

03Knowledge in the Head and in the World
Memory is unreliable and effortful. Good design externalises knowledge — putting information in the environment rather than requiring it in the user's head. Constraints, signifiers, and natural mappings all serve to make correct use discoverable without memorisation.
knowledge in worldmemoryconstraintnatural mapping
p. 71
04Knowing What to Do: Constraints, Discoverability, Feedback
Constraints prevent errors by limiting possible actions. Physical, cultural, semantic, and logical constraints all guide users toward correct behaviour. Discoverability — being able to figure out what actions are possible — is a fundamental usability requirement.
constraintdiscoverabilityphysicalcultural
p. 109
05Human Error? No, Bad Design
Human error is always a symptom of bad design. Norman distinguishes slips (correct intention, wrong execution) from mistakes (wrong goal entirely). Design can prevent both — through better affordances, forcing functions, confirmation dialogs, and reversible actions.
human errorslipmistakeforcing function
p. 147
Design ThinkingDesign in the World

Good design is a process: observe, generate ideas, prototype, test, and iterate. Human-centred design puts real user behaviour — not imagined rational behaviour — at the centre. Norman closes by addressing the tension between design ideals and business realities, and the growing complexity of designing for a connected world.

06Design Thinking
Human-centred design (HCD): observe real users, generate many ideas, prototype early, test with real users, iterate ruthlessly. The double diamond model — discover, define, develop, deliver — frames the process. Fail fast and fail safely during the ideation phase.
HCDprototypeiterateobserve
p. 217
07Design in the World of Business
Business pressures — time, cost, features, committee decisions — systematically push against good design. Norman explains why incremental improvements often beat radical redesigns, and why good design requires advocates at every level of an organisation.
businessincrementalcommitteecomplexity
p. 259
PDF Viewer— / —
📖

Loading PDF…

Just a moment.