Podcast thumbnail

The Design of Everyday Things

14 min
4.7

Introduction

Nova: Picture this. You walk up to a glass door at a coffee shop. You see a handle. You grab it. You pull. Nothing happens. You pull harder. Still nothing. Then someone behind you leans over and just... pushes. The door opens instantly. You feel like an idiot. Sound familiar?

Nova: Here's the thing, Sage. It was not you. It was never you. That door you just wrestled with has a name. In the design world, it is called a Norman Door, named after Don Norman, the author of one of the most influential books ever written about design. And the core argument of that book, The Design of Everyday Things, is that when you struggle with an everyday object, it is almost always the design that has failed, not the user.

Nova: Originally published in 1988 under the title The Psychology of Everyday Things and then revised and expanded in 2013, this book essentially created the blueprint for modern user experience design. Don Norman is a cognitive scientist who worked at Apple as Vice President of Advanced Technology and co-founded the Nielsen Norman Group. He looked at everyday objects through the lens of psychology and asked a simple but radical question: why do so many things we use every day make us feel stupid?

Nova: Exactly. And it turns out the answer to why things frustrate us reveals something profound about how our minds actually work.

Affordances, Signifiers, and Why We Blame Ourselves

The Norman Door and the Psychopathology of Everyday Things

Nova: Let's start with that door, because it is the most famous example in the book, and it perfectly illustrates the core problem Norman is diagnosing. He calls the opening chapter The Psychopathology of Everyday Things, which is a brilliant phrase. The idea is that everyday objects can be clinically confusing.

Nova: Not when you hear the design principle behind it. Norman introduces the concept of affordances. An affordance is the relationship between an object and a user that determines what actions are possible. A door affords opening. A chair affords sitting. A button affords pressing. Simple enough. But the problem is that affordances need to be perceivable. You need to be able to look at something and instantly know what to do with it.

Nova: Exactly. And that wrong signal is what Norman calls a failed signifier. In the 2013 revision of the book, he actually introduced the term signifiers to clarify this distinction. An affordance is what is possible. A signifier is the clue that tells you what to do. A flat metal plate on a door is a signifier that says push me. A vertical bar handle is a signifier that says pull me. When the signifier contradicts the affordance, you get a Norman Door.

Nova: And here is the truly insidious part. Norman points out that when we encounter a poorly designed object and struggle with it, our first instinct is almost always to blame ourselves. I am bad at technology. I am clumsy. I just do not get this thing. We internalize the failure.

Nova: We all have. And Norman argues that this is a cultural problem. In our society, we tend to blame people for errors rather than examining the systems and designs that made those errors likely or even inevitable. He cites the statistic that 75 to 95 percent of industrial accidents are attributed to human error. But when you dig deeper, you find that people were placed in situations where the design practically guaranteed mistakes.

Nova: And that reframing is the foundation of everything Norman teaches. He calls it human-centered design. It starts with accepting human behavior the way it is, not the way we wish it would be.

Execution, Evaluation, and the Seven Stages of Action

Bridging the Two Gulfs

Nova: Now let's go deeper into the psychology. Norman opens one of the most memorable chapters of the book with a story. He is at a conference in Italy, and a speaker tries to thread film onto a projector he has never used before. It takes fourteen minutes, multiple people, three languages, and eventually a blue-coated technician who swoops in and fixes everything in seconds.

Nova: Norman uses this moment to introduce what he calls the two gulfs. The Gulf of Execution and the Gulf of Evaluation. Every time you interact with any object, you have to cross these two gulfs. The Gulf of Execution is the gap between what you want to do and what the object actually allows you to do. In the projector example, the speaker wanted to thread the film, but the required sequence of actions was long, complex, and not at all obvious.

Nova: Precisely. And the Gulf of Evaluation is the gap between what the object does and your ability to understand what just happened. Even after the film was threaded, nobody could tell if it was done correctly. The system gave no clear feedback. Both gulfs were wide open, and the users fell right in.

Nova: That is a textbook Gulf of Evaluation problem. And Norman actually uses the VCR recording example in the book. The user thinks, I just want to press record, but the system requires four or five steps: press record, specify the time, select the channel, save the settings. The gulf between intention and action is enormous.

Nova: Norman maps out what he calls the Seven Stages of Action. Every interaction follows this cycle. It starts with a goal, then moves through three execution stages: you form a plan, you specify the steps, and then you perform them. After that come three evaluation stages: you perceive what happened, you interpret what it means, and you compare it against your original goal. Seven stages, and at each one, the design either helps you or abandons you.

Nova: It is. And the genius of it is that it gives designers a checklist. For every stage, you can ask: is the user supported here? Can they know what to do? Can they tell what happened? If the answer is no at any stage, you have found a design flaw. Norman says the information that helps users with the execution stages is called feedforward, knowing what you can do next. And the information that helps with evaluation is feedback, knowing what just happened.

Discoverability, Feedback, and Conceptual Models

The Seven Principles That Make Design Invisible

Nova: So we have diagnosed the problem. Now let's talk about the solution. Norman lays out seven core principles for good design. And these principles have become so foundational that they are essentially the Ten Commandments of the UX field.

Nova: First, visibility. The more visible a function is, the more likely people will know about it and use it. Norman gives the example of modern stoves. On many stove tops, the controls are placed on the back panel, and you have to guess which knob controls which burner. Compare that to a design where the knobs are arranged in the same spatial pattern as the burners themselves. That brings us to the second principle: mapping. Good mapping means there is a clear, natural relationship between controls and their effects.

Nova: Mercedes-Benz does this beautifully, and Norman cites it as a perfect example of natural mapping. The third principle is feedback. Every action must produce an immediate, clear response. When you press a button on your phone and it gives a subtle vibration, that is feedback. Without it, you press again, and again, and suddenly you have sent three texts.

Nova: Exactly. Fourth, affordances. We talked about this. The object should communicate what it can do. A chair affords sitting. A button affords pressing. Fifth, signifiers. The clues that point to the affordance. The label, the color, the shape, the sound.

Nova: Perfectly put. Sixth, constraints. This is about limiting what the user can do to prevent errors. Physical constraints are the most powerful. A square peg cannot go into a round hole. A USB-A plug can only go in one way. Norman describes forcing functions, a specific type of constraint where you cannot proceed to the next step without completing the current one. The classic example: you cannot start most cars without having the key present. The system physically prevents a dangerous error.

Nova: The conceptual model. This might be the most important one. A conceptual model is a simplified explanation in the user's mind of how something works. It does not have to be technically accurate, but it has to be useful. The files and folders on your computer are a conceptual model. There are no actual manila folders inside your hard drive, but the metaphor works. A good designer communicates a clear conceptual model through what Norman calls the system image: everything the user sees, touches, and hears. When the system image is clear, the user builds an accurate mental model. When it is confusing, the user forms a wrong model and makes mistakes.

Nova: That is beautifully said. And it is much harder than it sounds. Norman notes that good design is actually harder to notice than bad design, because good design fits our needs so perfectly that it becomes invisible.

Slips, Mistakes, and Designing for Imperfect Humans

Human Error Is Really Bad Design

Nova: Now we come to perhaps the most provocative argument in the entire book. Norman devotes an entire chapter to human error, and his core thesis is that most of what we call human error is actually bad design.

Nova: Norman would say yes, at least partly. He makes a crucial distinction between two types of errors. Slips and mistakes. A slip is when you intend to do the right thing but accidentally do the wrong thing. You meant to press save, but your finger hit delete. That is a slip. A mistake, on the other hand, is when you form the wrong goal or the wrong plan. You decide to take an action that is inappropriate for the situation because you misunderstood how the system works.

Nova: Exactly. And Norman argues that both can be mitigated through design. For slips, you design safeguards and confirmation steps. That is why your email asks, are you sure you want to send this without a subject line? For mistakes, you improve the conceptual model and provide better feedback so the user understands the state of the system.

Nova: And that is exactly the point. A well-designed system assumes that users will make errors and builds in protections. Norman writes, quote, if the system lets you make the error, it is badly designed. And if the system induces you to make the error, then it is really badly designed.

Nova: Norman acknowledges this. He does not claim that all errors can be eliminated. But he argues that we consistently underestimate how much design can reduce errors. He points to aviation as an example. Modern airplane cockpits are incredibly complex, but through careful, human-centered design, error rates have been dramatically reduced. Checklists, clear feedback, physical constraints that prevent wrong actions. These are all design solutions to human fallibility.

Nova: That is literally one of Norman's key insights. He writes, complexity is good; it is confusion that is bad. A complex object can still be understandable and usable if it is well-designed. The problem is not that things are complicated. The problem is that they are complicated without being clear.

Human-Centered Design in the Real World

Design Thinking and the Book's Lasting Legacy

Nova: Let's zoom out and talk about the bigger picture Norman paints in the later chapters of the book. He introduces design thinking as the process that brings all these principles together. And he describes two powerful frameworks: human-centered design and the double-diamond model.

Nova: It is actually from the British Design Council. It is a way of visualizing the design process. It has four stages: discover, define, develop, and deliver. The first diamond is about finding the right problem. You diverge, exploring broadly, then converge on a single problem statement. The second diamond is about finding the right solution. You diverge again, generating many ideas, then converge on the best one. Norman argues that the most common failure in design is solving the wrong problem beautifully.

Nova: That is exactly the mindset. And this connects to human-centered design, which Norman describes as a cycle of four activities: observation, idea generation, prototyping, and testing. You watch real people struggle with real problems. You generate ideas without constraints. You build quick, rough prototypes. You test them and learn. Then you do it all again. It is iterative, not linear.

Nova: Norman is refreshingly honest about this. He does not pretend that the principles are easy to follow in the real world. He acknowledges competitive forces, time pressure, and cost constraints. He even lays out what he calls Norman's Law of Product Development: the day a product development process starts, it is behind schedule and over budget. But he insists that the principles are still worth fighting for because the cost of bad design, frustrated customers, abandoned products, even accidents and deaths, is far greater than the cost of doing design right.

Nova: That might be the most remarkable thing about this book. Norman addresses this directly in the 2013 revised edition. He writes, our technologies may change, but the fundamental principles of interaction are permanent. The psychology of how humans perceive, understand, and act has not changed in thousands of years. A touchscreen is new, but the need for clear feedback, good mapping, and discoverable affordances is exactly the same. If anything, the principles are more relevant now, because we are surrounded by exponentially more designed objects and interfaces than we were in 1988.

Nova: Yes. And that is why it has sold millions of copies, why it is required reading in design schools worldwide, and why terms like affordance and Norman Door have entered the design lexicon. Don Norman gave us a vocabulary for understanding why things frustrate us and a framework for making them better.

Conclusion

Nova: So let's bring this together. We started with a door that made you feel foolish, and we ended with a complete framework for understanding how design shapes every interaction in our lives.

Nova: And that is the first and most important takeaway. When you encounter a frustrating object, ask not what is wrong with you, but what is wrong with the design. The second takeaway: great design is built on timeless principles. Visibility, feedback, affordances, signifiers, mapping, constraints, and a clear conceptual model. These are not trends. They are rooted in how the human mind works. The third takeaway: error is not a moral failing. It is a design opportunity. Build systems that assume people will make mistakes and protect them when they do.

Nova: Because you are a user. Every single day, you interact with dozens of designed objects and interfaces. Understanding the principles of good design makes you a more informed consumer, a more articulate advocate for better products, and honestly, it makes everyday life slightly less frustrating. Once you see bad design, you cannot unsee it, but you also stop blaming yourself for it.

Nova: That is the goal. Design that disappears. Design that works so seamlessly you never think about it. And achieving that invisibility takes enormous thoughtfulness, empathy, and an understanding of the principles Norman spent decades refining. The next time you use a product that just works, take a moment to appreciate the invisible design behind it. And the next time you push a door that should have been pulled, just smile and say, aha, a Norman Door.

00:00/00:00