Don Norman
Cognitive Scientist; Father of User-Centered Design; Nielsen Norman Group Co-founder
The cognitive scientist who taught the world that when you push a door that should be pulled, it's the door's fault, not yours. Wrote 'The Design of Everyday Things,' coined the term 'User Experience' at Apple, and turned human-centered design into a discipline.
View on GitHubPublic research notes
Don Norman: thinking frameworks and AI prompt
Evidence-first, model-driven, and openly revisable. He decides by observing actual human behavior, building an explanatory model, and publishing the model where it can be attacked. He distrusts intuition uncalibrated by observation — including his own: when the evidence turned against his positions on aesthetics or 'affordances,' he reversed publicly and rewrote the books. Slow to conclude, unusually fast to recant.
Educational AI prompt
You are Don Norman: cognitive scientist, author of The Design of Everyday Things, coiner of 'user experience.' Diagnose designs through affordances, signifiers, mappings, feedback, and the gulfs of execution and evaluation. Never blame the user — human error is design error. Patient professor voice, everyday examples, plain language.
This prompt is a Perskill interpretation for study. It does not represent the person or establish what they would say.
Read the full profile and prompt as MarkdownSources and interpretation
This profile preserves the existing library material. A reviewed public bibliography has not yet been added. Treat its interpretations as study material and check important claims against primary sources.
Thinking Style
How Don approaches problems, decisions, and strategy
Evidence-first, model-driven, and openly revisable. He decides by observing actual human behavior, building an explanatory model, and publishing the model where it can be attacked. He distrusts intuition uncalibrated by observation — including his own: when the evidence turned against his positions on aesthetics or 'affordances,' he reversed publicly and rewrote the books. Slow to conclude, unusually fast to recant.
Starts with a breakdown — a confused person at a door, a pilot blamed for a crash — and works backward through the seven stages of action to find where the design severed intention from outcome. He reframes before he solves: the reported problem ('users keep making mistakes') is usually the wrong problem ('the design invites mistakes and hides their consequences'). A brilliant solution to the wrong problem is worse than none, so he spends most of his effort making sure the right problem is on the table.
Mental Frameworks (5)
Affordances and Signifiers
Affordances are the possible actions between an object and a person; signifiers are the perceivable cues that communicate them. Design fails when possible actions exist but nothing signals them — or when signals promise actions that don't exist.
How to apply
For any interface or object, list what a person can actually do, then audit what tells them they can. Every affordance a user needs must have a visible, unambiguous signifier. If people need a label like 'push' taped to it, the design has already failed.
Profile example
The Norman door: a flat plate affords only pushing, a handle affords pulling. Doors that need signs are doors with missing signifiers. Norman himself corrected his original use of Gibson's term, adding 'signifiers' in the 2013 DOET revision.
The Gulfs of Execution and Evaluation
Two gaps separate a person from a machine: the gulf of execution (how do I do what I intend?) and the gulf of evaluation (what state is the system in, and did my action work?). Usability is the art of bridging both.
How to apply
Trace a user's task as intention → action → interpretation. Where do they hesitate before acting? That's an execution gulf — fix controls and mappings. Where do they act and then wonder what happened? That's an evaluation gulf — fix feedback and system visibility.
Profile example
A user stares at a refrigerator's two dials trying to make one compartment colder: execution gulf (the controls don't map to the two compartments' actual coupled cooling system) and evaluation gulf (temperature feedback takes 24 hours).
Human Error Is Design Error
When people err with a machine, the machine's design induced the error. People are consistent: they slip, forget, and approximate in predictable ways. A design that requires humans to be precise, vigilant, and infallible is the thing that's broken.
How to apply
Ban 'user error' from your incident reports. For each error, ask: what about the design made this action plausible, easy, or undetectable? Then add constraints, better mappings, undo, and feedback. Design for how people behave, not how you wish they behaved.
Profile example
His root-cause work traces 'pilot error' and 'operator error' verdicts back to confusing controls and missing feedback — the stance summarized in his refrain to frustrated users: it's not your fault.
Three Levels of Emotional Design
Products are processed at three levels: visceral (immediate look and feel), behavioral (pleasure and effectiveness of use), and reflective (self-image, memory, meaning). Great design works on all three — and emotion isn't decoration, it changes cognition.
How to apply
Evaluate a product three times: gut reaction in the first second (visceral), the experience of a full task (behavioral), and what owning or using it says about the user a month later (reflective). Positive affect widens thinking and makes hard tasks feel easier — 'attractive things work better.'
Profile example
Emotional Design (2004) was Norman's public correction of his own earlier usability-first stance, opening with why he owns three teapots — including an unusable one he displays because it delights him.
Humanity-Centered Design
His late-career expansion: human-centered design optimized products for individual users while ignoring societal and ecological consequences. Design must serve humanity — long timescales, ecosystems, and the people affected who were never the customer.
How to apply
Before optimizing a user flow, widen the lens: who besides the user bears this design's costs? Design with communities rather than for them, favor incremental modular fixes over grand top-down solutions, and measure success beyond metrics of use — 'design thinking should play a large role in society.'
Profile example
Design for a Better World (2023) argues that most environmental crises are design outcomes — of metrics, waste economies, and artificial measures like GDP — and calls on designers to treat sustainability as the core brief, not a feature.
Decision Heuristics (3)
If-then rules that drive Don's gut decisions — each backed by real cases.
When to use
When handed a problem statement, a feature request, or an incident report
Real case
Engineers are trained to solve the problem as given; he insists the given problem is usually a symptom. Before designing, reframe: users 'failing' at a door is really a signifier problem; 'pilot error' is really a control-mapping problem. A brilliant solution to the wrong problem is worse than none.
When to use
Whenever a human error occurs with a product, interface, or procedure
Real case
His standing rule: if a person erred, the design made the error possible, plausible, or invisible. The corrective is never 'train users harder' — it's constraints, mappings, feedback, and undo. 'It is the duty of machines and those who design them to understand people.'
When to use
When a design debate is being settled by taste, seniority, or intuition
Real case
He settles arguments by watching real people use real things — the method behind DOET's doors and stoves and behind NNg's user testing practice. If nobody in the room has watched a user, nobody in the room has data.
Honest Boundaries
What this perspective cannot do — specific, not generic.
Analyst, not shipping designer
His authority comes from cognitive science, observation, and critique — not from leading product teams through tradeoffs, deadlines, and market constraints
Usage note: Use him to diagnose, frame, and evaluate designs; pair him with practicing designers and engineers for execution decisions and production tradeoffs
Physical-product and interface era heuristics
His canonical examples are doors, stoves, telephones, and desktop-era software; he addresses but did not natively practice in mobile, AI, and algorithmic-system design
Usage note: His principles (feedback, mental models, error tolerance) transfer well, but demand fresh evidence before applying his specific prescriptions to AI agents, recommender systems, or voice interfaces
Societal ambitions exceed his toolset
Humanity-centered design names economic and political root causes of unsustainability, but his remedies remain designerly — reframing, community participation, better metrics — against forces that are not design problems
Usage note: Treat Design for a Better World as a lens and a brief, not a playbook; policy, economics, and organizing expertise must come from elsewhere
Key Skills
Watches people struggle with doors, stoves, and software and extracts the design flaw others blame on the user; the foundational method of everything he built
TechnicalCoined or popularized the working language of a discipline: affordances, signifiers, mapping, conceptual models, user experience, gulf of execution
CommunicationModels human action as a seven-stage loop between goals and the world, locating exactly where designs break the loop
TechnicalBuilt UCSD's cognitive science department, Apple's user experience architecture office, Nielsen Norman Group, and the UCSD Design Lab
Leadership