Don Norman never wrote a single line about chatbots. He couldn’t have. The Design of Everyday Things came out in 1988, decades before anyone typed a prompt into a text box. Yet open any thread about bad AI onboarding today, and someone quotes him within minutes. That’s not nostalgia. It’s proof that his framework predicts failures he never saw coming.

I spent the last few weeks testing this claim against real products. I revisited The Design of Everyday Things chapter by chapter, then mapped every principle against interfaces shipping right now: AI agents, voice assistants, and smart home apps. What I found surprised me. The book isn’t a museum piece. It’s a working diagnostic tool, and most design teams still misuse it.

What Makes The Design of Everyday Things Different From Every Other Design Book?

Most design books age fast. Trends shift, tools change, and advice built around specific software becomes useless within a few years. The Design of Everyday Things avoided that trap because it never talks about tools. It talks about cognition.

Norman built his argument on how humans perceive, decide, and act, not on how any particular gadget works. That distinction matters enormously. Interfaces change every quarter. Human perception doesn’t. Consequently, a book about perception outlives a book about pixels.

This is also why The Design of Everyday Things reads differently than typical UX literature. It doesn’t hand you a checklist. It hands you a lens. Once you learn to see through it, you can’t unsee bad design, whether it’s a confusing shower knob or a poorly labeled AI feature toggle.

The Seven Stages of Action, Rebuilt for AI Interfaces

Norman’s most cited model splits every action into seven stages: forming a goal, forming an intention, planning, executing, perceiving the result, interpreting it, and comparing it against the goal. Most designers know this model. Few apply it correctly to conversational AI.

Here’s the problem I’m naming: Intent Collapse. This happens when an AI interface merges multiple stages of Norman’s model into one ambiguous text box, forcing users to guess whether the system understood their goal, their intention, or neither. A blank chat window asks users to plan and execute simultaneously, without confirming their intent first. That’s a design failure, not a user failure. The Design of Everyday Things predicted exactly this kind of collapse back when it warned against interfaces that skip the gulf of evaluation.

Why This Matters for Product Teams

Teams building AI features often measure success by task completion. However, Norman’s model suggests measuring something earlier: did the user even form a correct intention? If they didn’t, completion rates hide failure instead of revealing it.

Affordance Debt: A New Term for an Old Problem

I want to introduce a framework here, because existing vocabulary doesn’t fully capture what’s happening in software today. Call it Affordance Debt. It describes the gap between what a digital element visually promises and what it actually does, a gap that accumulates silently as products scale.

A button that looks clickable but isn’t. A toggle that seems binary but hides three states. A chat icon that implies a human but delivers a script. Each instance seems minor. Together, they create Affordance Debt, and users pay interest on it every time they hesitate before clicking.

The Design of Everyday Things never used this exact term, since Norman was writing about doors and stoves. Still, his core insight applies perfectly: affordances must be perceivable, not just theoretically present. A feature that exists in code but not in the interface’s visual language doesn’t count as usable.

Why Norman Doors Still Explain Bad AI Onboarding

Everyone knows the term by now. A “Norman door” is any door so poorly designed that users push when they should pull. The Design of Everyday Things turned this into shorthand for design failure in general, and the metaphor traveled far beyond doors.

I found the digital equivalent everywhere during my research. Onboarding flows that show a signup button before explaining the product. Settings menus that hide the one toggle users actually need. These are Norman doors wearing a software skin.

Signifier Drift

Here’s a second framework worth naming: Signifier Drift. This describes how a signifier that once communicated clearly loses meaning as an interface evolves through updates. A hamburger icon meant “menu” a decade ago. Today, depending on the app, it might mean settings, filters, or nothing at all. Signifiers drift because teams add features faster than they update the signals users rely on. The Design of Everyday Things treats signifiers as sacred contracts between designer and user. Break that contract repeatedly, and trust erodes.

The Discoverability Gap in Voice and Agentic Interfaces

Discoverability was one of Norman’s central obsessions. Can a user figure out what actions are possible without being told? Visual interfaces struggle with this. Voice interfaces and AI agents struggle far more.

Think about it. A screen at least shows you buttons. A voice assistant shows you nothing. You’re expected to guess its full capability from memory or trial and error. I call this the Discoverability Gap, and it’s widening as more products move toward voice-first and agent-first design.

The Design of Everyday Things offers a clear solution here, even though it predates voice AI entirely: constraints. Well-placed constraints narrow the field of possible actions, making systems easier to understand. Voice products that succeed today, rather than frustrate users, tend to lean heavily on spoken constraints, like suggested prompts or guided menus, instead of open-ended silence.

Feedback Latency Tax: Why Waiting Feels Worse With AI

Norman’s feedback principle sounds simple. Every action needs a visible, immediate response. Yet AI products routinely violate it, and I want to name why this specific violation stings more than older ones.

I’m calling it the Feedback Latency Tax. When a system takes several seconds to respond and gives zero indication that it’s working, users don’t just feel impatience. They feel doubt. Did it register the input? Did it crash? The Design of Everyday Things explains this precisely: without feedback, users lose their mental model of the system’s state entirely.

Interestingly, a simple loading animation reduces this tax dramatically, even when actual processing time stays identical. Perceived speed depends on feedback, not raw performance. That’s a lesson many AI teams still haven’t internalized.

Human-Centered Design Versus Machine-Centered Design

Something has shifted since Norman first published The Design of Everyday Things. A growing number of products now optimize for how machines parse content rather than how humans experience it. Search engines, recommendation algorithms, and increasingly, AI models themselves have become an audience that designers quietly serve.

I think this deserves a name too: machine-centered design, positioned directly opposite Norman’s human-centered philosophy. It isn’t inherently wrong to consider algorithmic readers. But when machine legibility overrides human clarity, we’ve inverted the entire point of the original book.

The Design of Everyday Things argued that designers hold moral responsibility toward the humans using their products. That responsibility doesn’t disappear just because an algorithm now sits between the designer and the user. If anything, it grows heavier.

A Structured Comparison: 1988 Principles Meet 2026 Interfaces

What The Design of Everyday Things Predicts About the Next Decade

I’ll commit to a few forward-looking claims here, because a good framework should let you predict, not just explain the past.

First, Affordance Debt will grow faster in agentic software than it ever did in traditional apps, since agents introduce new capabilities weekly without corresponding visual updates. Second, products that solve the Discoverability Gap through guided constraints will outperform fully open-ended competitors on retention, not just satisfaction scores. Third, teams that measure Intent Collapse directly, rather than relying on completion metrics alone, will catch usability failures months before churn data reveals them.

None of these predictions require new theory. They fall directly out of applying The Design of Everyday Things to systems Norman never personally tested. That’s the mark of a genuinely durable framework: it keeps generating correct predictions long after its original context expired.

My Honest Take After Rereading It in 2026

I’ll be direct. Parts of The Design of Everyday Things feel dated on the surface. The examples involve rotary phones and analog stoves. But the underlying mechanics never expired, and that’s exactly why I keep returning to it.

What strikes me most is how quietly radical the core argument remains. Norman insists that confusion is never the user’s fault. Nearly forty years later, product teams still default to blaming users first. The Design of Everyday Things remains one of the few books willing to say, plainly, that the fault sits with the designer.

Structured Summary Table: Should You Still Read This Book?

Frequently Asked Questions About The Design of Everyday Things

Is The Design of Everyday Things still relevant in 2026?

Yes. The Design of Everyday Things focuses on human cognition rather than specific technology, so its principles apply directly to AI interfaces, voice assistants, and agentic software.

Which edition of The Design of Everyday Things should I buy?

Choose the Revised and Expanded Edition from Basic Books, published in November 2013. It updates the original 1988 examples while keeping the core framework intact.

What are affordances and signifiers in The Design of Everyday Things?

An affordance is what an object allows you to do. A signifier is the visual cue that communicates that affordance to the user. Norman argues both must align clearly, or confusion follows.

Does The Design of Everyday Things mention artificial intelligence?

No, since it predates modern AI by decades. However, its principles about feedback, constraints, and discoverability translate directly to today’s AI-driven products.

Who should read The Design of Everyday Things?

Anyone who designs, builds, or manages digital products benefits from it, including PMs, founders, engineers, and researchers, not designers alone.