The Design of Everyday Things
Source: https://www.basicbooks.com/titles/don-norman/the-design-of-everyday-things/9780465050659/ ↗
Norman introduced the concepts of affordances, signifiers, mapping and feedback to a popular audience and argued that when people struggle with designed objects, the fault lies with the design, not the user.
The book was originally titled The Psychology of Everyday Things and the rename to Design was itself a design decision — clarity over cleverness.
For product direction it is the canonical text on why usability matters and what specifically makes something usable or unusable; every designer knows the vocabulary, and every product director should.
Read alongside Gould and Lewis's Designing for Usability for the academic origin and Alexander's Notes on the Synthesis of Form for the deeper theory.
Norman's revised 2013 edition is the one to read.
Central argument
Norman argues that when people fail to use designed objects correctly, the cause is almost always bad design rather than user error — a claim he grounds in a specific vocabulary of concepts: affordances (what an object allows you to do), signifiers (what communicates that possibility), mapping (the relationship between controls and their effects), and feedback (how the system communicates what it has done). The central thesis is that good design makes the correct action visible and obvious, and bad design forces the user to rely on memory, guesswork, or manuals. Norman is making a normative, not merely descriptive, argument: designers are morally and professionally responsible for the difficulty users experience.
Critique
Norman's framework was built almost entirely on physical objects — doors, stoves, telephone keypads — and while the 2013 revision attempts to address digital interfaces, the conceptual machinery strains under conditions of software complexity: when an interface has thousands of possible states, non-linear flows, and personalized behavior, the clean causal story of 'bad signifier causes user failure' becomes harder to sustain. A deeper tension is that Norman's user is implicitly a single, capable adult encountering an object for the first time; the framework has less to say about habituated users, accessibility needs, or the social and organizational contexts in which products are actually used. This is not a flaw in the book so much as a boundary condition that product directors must recognize before universalizing its prescriptions.
Why it matters for product
For a product director, Norman's most operationally useful insight is the transfer of accountability: if users are not completing flows, not adopting features, or generating support volume, the design — not the user's sophistication — is the first place to look, which reframes how you should interpret product analytics and prioritize the backlog. The shared vocabulary Norman established (affordances, signifiers, mapping, feedback) is a genuine organizational asset because it gives cross-functional teams — design, engineering, research, product — a common language for diagnosing usability problems in review sessions without the conversation collapsing into taste or opinion. Where the book connects to strategy is subtler: Norman's principle that good design makes the right action the obvious action is directly applicable to activation and onboarding strategy, where the product director's job is to architect the path of least resistance toward the moment of value.