← Blog20 November 2026
ux5 min read

Books Like The Design of Everyday Things

Norman taught you to notice doors. These books teach you to notice pages, habits, and your own head — the full map of why things are confusing.

From Product Theory: The Hidden Forces That Shape User Behavior — 40+ short chapters on why users behave the way they do.


If you loved The Design of Everyday Things and want more, read Steve Krug for the web, Daniel Kahneman for the mind behind the mistakes, and John Maeda for when less is actually better. Norman taught you to notice doors. The best follow-ups teach you to notice something else — pages, habits, your own head — so the confusion stops looking like your fault and starts looking like a design choice.

Disclosure: one of the books below the list — Product Theory — is written by Spencer Shulem, who runs this blog. It is not in the ranked list and is not ranked first; it sits in its own clearly-marked note at the end. The six numbered picks were chosen on one test: does it change what you notice afterward?

The quick map

BookWho it's forThe one idea
The Design of Everyday ThingsAnyone frustrated by objectsBad design, not bad users
Don't Make Me ThinkWeb & app makersEvery click should be obvious
The Laws of SimplicityPeople drowning in featuresSubtract thoughtfully
Universal Principles of DesignReference-shelf buildersNamed patterns you can reuse
Thinking, Fast and SlowAnyone who designs for peopleYour own head misleads you
HookedProduct builders (read critically)Habits are engineered

1. The Design of Everyday Things — Don Norman (1988)

Read this if you've ever pushed a door that said pull and blamed yourself.

This is the root text. Norman — a cognitive scientist who later led design at Apple — coined the everyday meaning of affordances and gave us the "Norman door." His revised edition (2013) sharpened the language, but the lesson holds: when you struggle with a thing, the thing is usually at fault.

Two of the most important characteristics of good design are discoverability and understanding.

Drawback: it's a book of principles, not a how-to. If you want step-by-step tactics for shipping a screen this week, you'll finish inspired but still unsure where to click. More on Norman at the Nielsen Norman Group and his own site.

2. Don't Make Me Think — Steve Krug (2000)

Read this if you build or test websites and apps.

Where Norman is doors, Krug is pages. His whole argument fits in the title: usability means a user never has to stop and puzzle out what to do next. The revised "Revisited" edition (2014) adds mobile and a lean usability-testing chapter you can run with five people and a coffee.

Don't make me think!

That line is literally the book's first law, stated as his "first law of usability."

Drawback: it's deliberately thin and web-first. If you want deep cognitive theory or anything about physical products, this isn't it — that's a feature, not a bug, but know what you're buying. More at sensible.com.

3. The Laws of Simplicity — John Maeda (2006)

Read this if your product keeps growing features and losing its soul.

Maeda, an MIT Media Lab veteran, lays out ten laws for taking things away without making them worse. His first law — "Reduce" — is the one most teams need tattooed on their roadmap. It's a short book you can read in a sitting.

The simplest way to achieve simplicity is through thoughtful reduction.

Drawback: some laws read more like aphorisms than tools, and it's a product of its mid-2000s moment. You'll leave with a mindset, not a checklist. See the MIT Press page and Maeda's site.

4. Universal Principles of Design — William Lidwell, Kritina Holden & Jill Butler (2003)

Read this if you want a reference you'll open for years, not read once.

This is the opposite of a narrative book. It's a flip-through encyclopedia — each principle (Hick's Law, the aesthetic-usability effect, signal-to-noise ratio) gets two pages: definition on the left, example on the right. The expanded editions push past 125 entries.

I'm paraphrasing rather than quoting here, because the value is structural: it gives you names for patterns you've felt but couldn't point at — and a named thing is a thing you can design on purpose.

Drawback: breadth over depth. No entry goes deep, and read cover-to-cover it's dry. Use it as a lookup, not a page-turner. Publisher page at Quarto/Rockport.

5. Thinking, Fast and Slow — Daniel Kahneman (2011)

Read this if you design anything used by human beings — so, everything.

Norman is doors, Krug is pages, Kahneman is your own head. The Nobel laureate's two-system model — fast, intuitive System 1 and slow, effortful System 2 — explains why good defaults, clear framing, and reduced friction work. It's the engine under every design heuristic you already trust.

Nothing in life is as important as you think it is while you are thinking about it.

Drawback: it's long, academic in stretches, and some priming studies cited in it have weathered the replication crisis poorly — Kahneman himself publicly conceded on priming. Read it for the framework, stay skeptical of individual studies. Overview via his Nobel page.

6. Hooked — Nir Eyal (2014)

Read this if you want to see the machinery behind habit-forming products.

Eyal's "Hook Model" — trigger, action, variable reward, investment — is the clearest short map of how products wire themselves into your routine. Read it to notice the loop, whether you're building one or trying to quit one.

A habit is at work when users feel a tad bored and instantly open Twitter.

Drawback: it reads like a playbook for the same engagement patterns many of us now regret. Eyal wrote a follow-up, Indistractable (2019), partly in response. Pair them, and read Hooked with the ethics chapter front of mind. More at nirandfar.com.

If you only read one?

Start where you already feel the pain. Frustrated by objects? Norman. Shipping screens? Krug — it's the shortest path to a visibly better product this week. Want to understand why any of it works? Kahneman, and accept it'll take a month.

Rule of thumb: pick the book about the thing you're being paid to notice right now, not the one with the best reputation.

How did I choose these?

One test: does the book change what you see afterward? Generic UX listicles pad themselves with whatever's trending. These six each hand you a new lens — doors, pages, reduction, named patterns, your own biases, habit loops. I dropped anything that was a tactics manual with a short shelf life, and I didn't include ratings or sales numbers because they tell you nothing about whether a book will rewire your attention.

The one I wrote — Product Theory (Spencer Shulem, 2026)

Read this if you've absorbed the classics and want the connective tissue between them — the shared theory under why things confuse people.

I'll keep this honest because it's mine. Product Theory is the book I wanted after reading the six above: less "here's a door, here's a page," more "here's the underlying model that makes doors, pages, and minds all the same problem." It's newer and far less battle-tested than Norman or Kahneman, who've had decades to be proven right.

Where it falls short: if you specifically need to make a website less confusing this week, skip mine and read Krug — Don't Make Me Think is faster, more concrete, and will improve a real screen today. Come back for the theory once the fire's out.


If this map of "what each book teaches you to notice" was useful, subscribe to Context Limit — I send the next idea about why things confuse us, and how to design around it, straight to your inbox.