Design, Condensed

When a capable person fails at an everyday thing, the design is at fault, and that one inversion drives the whole discipline: a struggling user is reporting a design defect. Good design disappears because it fits how people perceive and act; bad design screams its inadequacies and gets blamed on the person holding it. Two questions gate quality — can I discover what to do, and can I understand what it means — answered by affordances made perceptible through signifiers, by mappings that put the control-to-effect relationship into the world, by feedback that closes the loop, and by a conceptual model the system image carries in full. Push memory into the world so remembering becomes unnecessary; narrow the action space with constraints and forcing functions; assume error and make every action reversible, because recurring error marks a design fault. On screens the object owns no physical affordances, so the front-end supplies every cue and the rendered surface is the entire system image. Beyond the interface, the same discipline runs outward: choice architecture decides behavior through defaults and friction before any persuasion starts; color carries function before decoration; the objects a person keeps are part of the designed environment, so owning fewer, better things is itself a design act; and good design is recognized by subtraction — the question is never what can be added, but what can be taken away. The examples date; the psychology does not, so the principles outlast the technology.

---

1. The thesis

• Blame the design, not the person. A capable user defeated by an everyday thing is evidence against the design; the door, not the doorway, failed (Design of Everyday Things).
• Good design disappears; bad design screams. Quality shows as absence of friction, so it is harder to notice than the failures that announce themselves (Design of Everyday Things).
• Difficulty is data. Read every struggle as a signifier of where the design can improve, never as a user defect (Design of Everyday Things).
• Two questions gate everything: can the user discover what actions are possible, and understand what they mean (Design of Everyday Things).
• Beauty and use coexist. Corrective cues can be supplied without destroying aesthetics; beauty bought by removing signifiers is the invisible-hinge failure (Design of Everyday Things).

2. The principles of discovery

• Affordance is a relationship, not a property. What an object lets an agent do exists whether or not anyone perceives it (Design of Everyday Things).
• The signifier is the perceptible cue, and for designers it outranks the affordance. A possibility nothing signals goes undiscovered (Design of Everyday Things).
• On screens the signifier is the whole job. A digital object has no physical affordance, so appearance and state carry every cue; a control that needs a tooltip has a failed signifier (Front-End Web Design).
• Natural mapping puts the control-to-effect relationship into space and slashes the memory it would otherwise cost (Design of Everyday Things).
• Feedback is immediate, informative, prioritized, and unobtrusive. Within ~0.1s; poor or overloaded feedback is worse than none (Design of Everyday Things).
• The system image carries the conceptual model. The designer never speaks to the user directly, so everything perceivable bears the whole burden of communication (Design of Everyday Things).

3. Action — seven stages, two gulfs

• Run a stuck flow against the seven stages and the failing one is locatable. Goal, plan, specify, perform, perceive, interpret, compare (Design of Everyday Things).
• Bridge the Gulf of Execution with feedforward: signifiers, constraints, mappings, defaults, a clear model (Front-End Web Design).
• Bridge the Gulf of Evaluation with feedback: visible status, confirmation, results read against the goal (Design of Everyday Things).

4. Knowledge in the world

• Make remembering unnecessary by putting the cue in the world. Recognition beats recall; show the options instead of demanding memory (Cognitive Load).
• Working memory holds three to five items and a single interruption wipes it, so chunk long values and split long steps (Cognitive Load).
• Never let needed information vanish at the moment it is needed — a code, a half-typed form, a result must survive navigation and failure (Front-End Web Design).
• The environment carries the cue. Putting the right thing in sight is the device version of arranging a room to set the default action (Environment Design).

5. Constraints and forcing functions

• Four constraints narrow toward the one right action: physical, cultural, semantic, logical; stack enough and instructions become unnecessary (Design of Everyday Things).
• Forcing functions make the dangerous move structurally impossible — interlocks sequence it, lock-ins hold it, lockouts bar it (Design of Everyday Things).
• A safeguard annoying enough to defeat gets defeated, so keep the friction local to the one risky step (Front-End Web Design).
• Standardize when no better solution exists, so the pattern is learned once and reused everywhere (Design of Everyday Things).

6. Error is bad design

• Recurring error marks a design fault; keep asking why past the human in the chain. “It should be called system error” (Design of Everyday Things).
• Accidents are holes lining up, not one culprit (Swiss cheese): add layers, shrink each layer’s holes, and alert when several have aligned (Design of Everyday Things).
• Slips and mistakes need different cures. Right-goal-wrong-execution wants distinct controls, visible modes, and resumable steps; wrong-goal wants clearer state and models (Design of Everyday Things).
• Assume error and make it reversible — undo is the strongest tool; sensibility-check absurd input and never make people start over (Front-End Web Design).
• Get the first contact right. An error costs far more than the careful step it replaces, so accuracy precedes speed in the design as in the doing (Accuracy Before Speed).

7. Beyond usability

• Design the visceral, behavioral, and reflective levels together; one bad ending poisons the remembered verdict of an otherwise good product (Design of Everyday Things).
• Attractive things work better, because positive affect widens tolerance and creativity when minor trouble appears (Design of Everyday Things).

8. Process and the long view

• Solve the right problem before solving it well — diverge then converge twice, the double diamond (Design of Everyday Things).
• Requirements come from watching people in context, not from asking or theorizing; most cases are special, and a system that forbids special cases fails (Design of Everyday Things).
• Design for the activity and the result serves everyone; there is no average person, so prefer flexible and adjustable (Design of Everyday Things).
• Featuritis is the default trajectory; defend coherence. Matching a rival feature-for-feature converges every product toward sameness (Design of Everyday Things).
• Legacy and habit beat a superior design that demands relearning, the way QWERTY outlasts the faster Dvorak (Design of Everyday Things).
• The principles outlast the technology. Devices change; the psychology of interaction does not (Design of Everyday Things).

9. Choice architecture — the nudge layer

• The default is the most powerful decision a designer makes, because most people keep it; whoever sets the default has chosen for the majority (Thaler & Sunstein, Nudge — owner page owed).
• Friction steers. Making the good action one step easier and the harmful one one step harder redirects behavior without removing choice; the same mechanism run against the user is the dark pattern (Thaler & Sunstein, Nudge — owner page owed).
• Salience is a budget. What is visible gets chosen; burying an option is functionally removing it for most users, which is a power to spend deliberately (Thaler & Sunstein, Nudge — owner page owed).
• Nudges owe transparency. A nudge the user would object to on discovery is manipulation wearing design’s clothes; the test is whether the architecture survives being explained to the person inside it (Thaler & Sunstein, Nudge — owner page owed).
• The environment version is already doctrine here: the room cues the action and sets the default before willpower enters (Environment Design).

10. Color

• Color carries function before decoration. State, grouping, and hierarchy come first; a palette that only decorates is spending the channel on nothing (model-sourced — owner page owed).
• Contrast is load-bearing. Text and controls live or die on figure-ground separation, and low-contrast interfaces fail exactly the users with the least margin; contrast standards exist and are checkable (model-sourced — owner page owed).
• Color is never the only channel. Roughly one in twelve men reads red-green poorly, so every color-coded meaning needs a second carrier — shape, position, label (model-sourced — owner page owed).
• Fewer hues, more shades. A palette of one or two hues with tonal range reads as designed; many hues at equal weight read as noise. The 60-30-10 split (dominant, secondary, accent) is the standard starting ratio (model-sourced — owner page owed).
• Meaning stays consistent. A color that means “danger” in one screen cannot mean “featured” in the next; the palette is a small language, and languages keep their words (model-sourced — owner page owed).

11. Owning things is design

• Every kept object is a running cost in attention, space, and maintenance — the room is an interface, and clutter is its featuritis (Ownership Cost, Minimalism as Systems Design).
• Discarding is a skill with rules, not a mood. The tells for removal: kept for “someday,” kept from guilt, kept in duplicate, kept unused for a year — each names a thing owning the person rather than the reverse (Fumio Sasaki, Goodbye, Things — owner page owed).
• Things broadcast. Possessions transmit self-image, and curating them is designing the signal; fewer, truer objects say more (Fumio Sasaki, Goodbye, Things — owner page owed; Wanting Less).
• Choose products the way a designer would defend them: one clear job, honest materials, signifiers intact, repairable, and still wanted when the novelty is gone — the purchase is an audition against the discard rules above (Sasaki + Rams, synthesized — owner page owed).

12. Finding good design

• Focus is saying no. A thousand no’s for every yes; the discipline is deciding what the thing will not do, and featuritis is what saying yes looks like from inside (Jobs, via the Cook interview in raw/processed — owner page owed).
• Simplicity is conquered complexity, not absence. Making something simple is hard work moved from the user into the design; simplicity achieved by omission is just a missing feature (Jobs — owner page owed).
• Design is how it works. Appearance is the last layer, not the definition; a beautiful thing that works badly is bad design wearing makeup (Jobs — owner page owed).
• Rams’ test compresses to one line: good design is as little design as possible. Useful, understandable, honest, long-lasting, unobtrusive — and the fastest audit of any object is asking what could be removed without loss (Dieter Rams, ten principles — owner page owed).
• Taste trains like any skill: study objects that survived decades, name what they refuse to do, and run the removal question until it becomes a reflex — the design version of comparing to standards, not to the small pond (Loss Aversion on comparison; Rams/Jobs — owner page owed).

---

Tension resolved: discoverability and deliberate difficulty pull against each other. Security, games, and learning are the cases where friction is the point, so hiding an affordance is defensible only when the difficulty serves the user — and even then it wants a discoverable way in. The applied version of that fight, plus the cross-surface and accessibility costs, lives in Front-End Web Design; a signifier with nothing behind it is the design cousin of The Shortcut Problem, visible activity that bypasses the real cognition.

Second tension resolved: sections 9 and 11 overlap Minimalism, Condensed by design (Wedge, 2026-07-03: the overlap is acceptable). The division: Minimalism owns the accounting — what ownership costs and why less pays; this page owns the design reading — the room as interface, the purchase as an audition, defaults and cues as the mechanism. One doctrine, two lenses, each page pointing at the other.

Source status (2026-07-03): sections 1–8 trace to published owner pages. Sections 9–12 were expanded at Wedge’s direction from external sources and model knowledge — Thaler & Sunstein’s Nudge, Fumio Sasaki’s Goodbye, Things, Dieter Rams’ ten principles, and the Jobs/Cook material (transcript in raw/processed) — and their lines are marked “owner page owed.” These are the condensed genre’s flagged gaps, not settled doctrine: each new section needs its owner page before this page’s no-new-claims rule holds again.

Omitted deliberately: the emotional layer across the three levels of processing, which has its own book and only a preview here. Owed before the doctrine is complete — dedicated pages for Affordances, Signifiers, Norman Doors, the Seven Stages of Action, Constraints, Forcing Functions, Designing for Error, Human-Centered Design, and Featuritis, each currently folded into Design of Everyday Things — plus new owner pages for Choice Architecture, Color in Interfaces, Discard Rules (Sasaki), and Focus & Simplicity (Rams/Jobs).