A Globusz Books discovery
The Design of Everyday Things
Don Norman · English
Design doesn’t just live in fancy gadgets or flashy apps — it’s in every doorknob that jams, every stove knob that confuses, every remote control that feels like a secret puzzle. Don Norman’s The Design of Everyday Things throws a spotlight on the silent war between humans and poorly made objects, arguing that when things go wrong, it’s usually the design’s fault, not yours.
Globusz Books summary
What the book is about
Don Norman’s The Design of Everyday Things is the antidote to the frustration we all feel when everyday objects refuse to cooperate. It’s not about blaming users for being dumb or impatient — it’s about calling out lousy design that ignores how people actually think and behave. Norman’s core point is simple but often overlooked: good design should be intuitive, obvious, and forgiving. When you struggle to figure out how a toaster works or why the light switch does nothing, that’s a failure of design, not a personal shortcoming.
The book dives into what makes design work or fail by breaking down the interaction between people and objects into a few key ideas. First up, affordances — the natural clues an object gives about how it can be used. Think of a chair: it affords sitting. But when designers don’t make affordances clear, confusion reigns. Then there are signifiers, which are the signals that tell you where to act, like a button labeled “push” or a handle shaped for grabbing. Without clear signifiers, you’re left guessing.
Constraints are another weapon in the designer’s toolkit. They limit what you can do, steering you away from mistakes. For example, a USB plug that only fits one way is using physical constraints to save you from flipping it around three times. Mappings link controls to their effects, so if you turn a knob to the right, the volume goes up. Poor mapping is why some stove knobs make you guess which burner you’re actually turning on.
Feedback is the final piece — it’s the immediate response you get after an action, confirming you did something right or alerting you that you messed up. Without feedback, you’re left in the dark, wondering if anything happened at all.
Norman peppers the book with examples that make you nod and cringe. He shows how complex technology often piles on layers of confusion instead of clarity. Instead of making things easier, designers sometimes make them more complicated, expecting users to read manuals or guess the hidden logic. This book is a call to put users first, to make products that don’t require a PhD to operate.
One of the biggest strengths of the book is its clarity. Norman writes like he’s explaining things to a friend who’s been driven crazy by a malfunctioning gadget. His ideas are practical, not academic fluff. This makes the book accessible to designers and curious readers alike. However, there’s a catch: the book was first published in the late ’80s and updated in 2013, so some of its examples and focus don’t fully capture the wild complexity of today’s digital interfaces and apps. It’s brilliant for physical objects and basic digital design but less so for the tangled ecosystems of modern software.
The Design of Everyday Things arrived at a time when the design world was just waking up to the importance of user experience. Norman helped shift the conversation from what technology can do to what humans can handle. His work laid the groundwork for human-centered design, which is now the gold standard in product development.
Reading this book makes you rethink your relationship with everything from door handles to smartphones. It’s a reminder that design shapes how we live, work, and even think. When done right, it fades into the background, letting you get on with your life. When done wrong, it’s an annoying roadblock that wastes your time and patience.
In short, The Design of Everyday Things isn’t just about design nerds geeking out. It’s about making the everyday less frustrating and more human. It’s a must-read if you want to understand why some things just work and others make you want to throw them out the window.
Beyond the summary
What might this book awaken in you?
Design isn’t magic or rocket science — it’s about understanding people and making things that just work. When objects confuse or frustrate you, it’s rarely your fault. Don Norman’s book reminds us that thoughtful design can make everyday life less annoying and more human. It’s a call to demand better from the stuff we use every day.
Before you commit
Why you might read this
Design doesn’t just live in fancy gadgets or flashy apps — it’s in every doorknob that jams, every stove knob that confuses, every remote control that feels like a secret puzzle. Don Norman’s The Design of Everyday Things throws a spotlight on the silent war between humans and poorly made objects, arguing that when things go wrong, it’s usually the design’s fault, not yours.
Themes worth noticing
Human-Centered Design
Focusing on people’s actual needs, behaviors, and limitations rather than just technology capabilities.
Usability and Intuition
Making products that feel obvious and easy to use without requiring manuals or guesswork.
Error Prevention and Forgiveness
Designing to minimize user mistakes and to recover gracefully when mistakes happen.
Psychology of Interaction
Understanding how human cognition and perception influence the way we use objects.
Key ideas, explained
Affordances and Signifiers: The Language of Objects
Objects should naturally suggest how to use them. Affordances are the possibilities an object offers, like a button you can press or a handle you can pull. Signifiers are the cues that highlight these affordances — a label, shape, or color that says "hey, this is where you act." Without these, users are left guessing, leading to confusion and mistakes.
Constraints and Mappings: Keeping Users on Track
Good design limits what you can do to prevent errors. Constraints physically or logically block wrong actions, like a USB plug that only fits one way. Mappings connect controls to their effects in a way that feels natural — turning a dial clockwise should increase, not decrease, volume. When these are off, users struggle and get frustrated.
Feedback: Closing the Loop
Feedback is how a product tells you what just happened. Did your command work? Is the oven heating? Without clear feedback, users are left in the dark, uncertain if they succeeded or failed. Immediate, understandable feedback keeps users confident and reduces errors.
User-Centered Design vs. Technology-Centered Design
Norman argues for design that starts with people’s needs and behaviors, not the capabilities of technology. Too often, designers get excited about what their tech can do and forget that users don’t want to read manuals or figure out complicated steps. Making things simple, visible, and forgiving is the path to better products.
Design Failures Are Not User Failures
When people mess up, it’s usually the design’s fault, not the user’s. Blaming users for errors ignores the responsibility of designers to make interfaces that accommodate human limitations. This shift in perspective is crucial for creating products that actually work for real people.
How to Use This Book in Real Life
Make Affordances Obvious
When designing or evaluating a product, check if it clearly shows how to use it. If it’s not obvious, add signifiers like labels, shapes, or colors that guide the user’s actions.
Use Constraints to Prevent Mistakes
Design should limit what users can do to avoid errors. Physical or logical constraints can save users from frustrating missteps, so think about how to block wrong actions naturally.
Ensure Clear Mappings
Controls should have an intuitive relationship with their effects. If turning a knob or pressing a button doesn’t feel logical, users will guess—and guess wrong.
Provide Immediate Feedback
Always let users know what just happened after an action. Whether it’s a beep, a light, or a message, feedback reassures users and prevents confusion.
Design for Real People, Not Ideal Users
Remember that users are busy, distracted, and imperfect. Design with empathy for human quirks and limitations instead of expecting perfect behavior.
What the book does especially well
- Clear, approachable writing that makes design principles easy to grasp.
- Practical, real-world examples that connect theory to everyday life.
- Shifts blame from users to design, promoting empathy and better products.
- Foundational influence on human-centered design and user experience fields.
Where the book gets shaky
- Some examples feel dated given the explosion of complex digital interfaces since 2013.
- Focuses more on physical objects and basic interactions than on software ecosystems.
- Doesn’t deeply explore advanced design methodologies or the latest UX research.
- Simplifies human behavior, which can be messier and less predictable than presented.
Questions to carry with you
- What clues does this object give me about how to use it — and are they clear?
- Where could design constraints prevent me from making mistakes?
- Does this product give me enough feedback to know what just happened?
- Are designers assuming I’m smarter or more patient than I really am?
- How might better design make my daily life less frustrating?
The bottom line
Design isn’t magic or rocket science — it’s about understanding people and making things that just work. When objects confuse or frustrate you, it’s rarely your fault. Don Norman’s book reminds us that thoughtful design can make everyday life less annoying and more human. It’s a call to demand better from the stuff we use every day.
Reader feedback
Was this summary useful?
Rate the Globusz summary of The Design of Everyday Things, not the book itself.
Loading reader ratings…
Where to go next
Don’t just read the nearest look-alike.
These recommendations serve different purposes: stay with the author, follow the closest idea, find an easier entry, go deeper, or deliberately change perspective.
Strong overlap in themes, life-impact signals, mood, or the questions the books raise.
Patrick Lencioni’s fable reveals the five deadly traps that can derail even the most capable CEOs. It’s less about business strategy and more about the human flaws leaders refuse to admit. What happens when protecting your image becomes more important than delivering real results? This book pulls back the curtain on leadership’s messy, uncomfortable truths.Read this summary →Also worth exploringThe Power of Pull: How Small Moves, Smartly Made, Can Set Big Things in MotionJohn Hagel III, John Seely Brown, Lang DavisonRelated through the themes, questions, or life-impact signals surrounding this book.
The Power of Pull reveals a quiet revolution in how we connect and create value by shifting from push-based mass production to pull-driven, real-time networks. What if success depended less on shouting louder and more on knowing exactly when and where to reach out? This book maps out how small, smart moves can draw the right people and resources to you—when you need them most.Read this summary →Also worth exploringCompetitive Strategy: Techniques for Analyzing Industries and CompetitorsMichael E. PorterRelated through the themes, questions, or life-impact signals surrounding this book.
Michael Porter’s "Competitive Strategy" exposes the hidden forces that determine who wins and loses in business. It’s not about fancy jargon or luck—it's about understanding the brutal realities of your industry and your rivals. Ready to see the market as it really is and make strategy that sticks?Read this summary →Also worth exploringComputers and Society: Computing for GoodJohn Impagliazzo, Leslie A. Carr (Editors)Related through the themes, questions, or life-impact signals surrounding this book.
Computers aren’t just about flashy gadgets or apps that make your life ‘easier.’ Sometimes, they’re quietly doing the heavy lifting against poverty, environmental destruction, and social injustice. This book doesn’t sugarcoat the tech world’s messiness but shows how some computing pros have rolled up their sleeves to actually do some good—warts and all.Read this summary →Also worth exploringContinuous Observability: A Practical Guide to Microservices Observability in the CloudBen Sigelman, Yuri Shkuro, Gardner MontgomeryRelated through the themes, questions, or life-impact signals surrounding this book.
Microservices in the cloud are like a sprawling city with millions of moving parts—and no one’s handing out maps. Continuous observability is the messy, relentless work of making sense of it all before things blow up. This book doesn’t sugarcoat it: if you want your cloud-native systems to behave, you need more than just dashboards and alerts—you need a whole new way of watching your software breathe and stumble.Read this summary →Technology relevance
Still relevant in 2026: Yes — foundational
Timeless principles of usability and design still apply today.
Topics: usability · user experience · design
Continue the journey
Read the original when you are ready.
The full book offers a richer, more nuanced look at how design shapes our interactions with the world. It’s packed with stories, examples, and explanations that make the concepts stick and invite you to see the world differently. Beyond the basics, Norman explores the psychology behind mistakes and how to design systems that forgive human error — a crucial insight for anyone involved in creating or using products. If you want to truly grasp why some designs work and others don’t, the full text is worth the time.