Sometimes, I land on a website and feel lost within 3 seconds. Other times, I click a button and wonder if it’s broken. Recently, I hit Cmd+Z to undo an input, and the site threw me back to the previous form step — erasing 20 minutes of work. 🤯

That’s bad usability.
It made me search for the usability book every developer, designer, and product manager should read - and I found it:
“Don’t Make Me Think” by Steve Krug.

🔍 Why I Picked It Up

After reading Start with Why by Simon Sinek, I built a habit of asking why — including why a book written over 20 years ago is still a top recommendation today.

Before starting, I scanned Goodreads reviews:

  • Some called it outdated.
  • Others said it was too basic. 🤔

So, I read it with 3 key questions in mind:

  • Which advice still holds up? ✅
  • What (if anything) feels outdated? 🕰️
  • Is it useful for developers, or just for designers? 🧑‍💻🧑‍🎨

🕵 3 Myths About This Book — Busted 💥

⌛️ Myth 1: It’s Outdated

✅ Reality: Only the technology examples feel old.
The core principles are timeless — exactly what Steve Krug predicted:

“Since it was about design principles and not technology, I didn’t think it was likely to be out of date anytime soon.”

Even today, the advice holds up.
The ideas also apply beyond design, like in habit formation: “Atomic Habits” teaches: make it attractive and reduce friction. That’s usability in real life. 👍

🧑‍💻 Myth 2: It’s Too Basic for UX Pros

✅ Reality: It’s simple on purpose — a usability guide for busy people.

The simplicity makes it accessible even for non-designers.
Humor, illustrations, and conversational tone make it one of the most enjoyable design books I’ve read. 👍

🙃 Myth 3: It’s All Common Sense

✅ Reality: If it’s so obvious, why do so many websites still get usability wrong?

It’s timeless advice — even 20+ years later, modern websites still break Krug’s basic rules. 👍

🔄 What Changed Since the Last Edition?

Here’s what evolved in the usability world since the book’s release:

Then Now
Simple usability testing A/B testing, heatmaps, remote testing
Basic layouts Grid systems, micro-interactions, motion design
Functional design Emotional design (branding, storytelling, gamification)
Accessibility optional Accessibility mandatory (WCAG, inclusive design)

📚 5 Practical Lessons You Can Use Today

🤔 Lesson 0: Don’t Make Me Think

If you only remember one rule — this is it.

🔎 Lesson 1: Users Don’t Read — They Scan

Developers often assume users read every word. They don’t.

Users hunt for what they need, scanning like this:

  • Google search results: You jump between bold text and headings, not full sentences.

✅ Make content scannable:

  • Short paragraphs
  • Clear headings
  • Bold keywords
  • Obvious buttons (no clever labels)

😌 Lesson 2: What Makes Something Usable?

Krug’s usability checklist still works today:

✅ Usability = Useful + Learnable + Memorable + Effective + Efficient + Desirable + Delightful

Attribute Question to Ask
Useful Does it solve a real need?
Learnable Can users figure it out quickly?
Memorable Will they remember how to use it?
Effective Does it get the job done?
Efficient Does it minimise effort?
Desirable Do users actually want it?
Delightful Is it enjoyable to use?

🎯 Lesson 3: Users Satisfice, Not Optimise

Users don’t search for the best option — they pick the first reasonable one.

✅ Design for satisficing:

  • Clear defaults
  • Fewer choices
  • Obvious next steps

👆 Lesson 4: Every Click Should Have a Clear Outcome

Users hate surprises — they want to know exactly what happens when they click.

✅ Make actions predictable:

  • Label buttons based on what happens next (e.g., “Next Step: Choose Your Plan” instead of just “Next”)
  • Avoid mystery meat navigation (unclear icons or vague links)
  • Use visual feedback after clicks (loading indicators, confirmation messages)

The less users wonder, the faster they move forward — and the happier they are.

✨ My Favourite Part: Positive Examples

What stood out was the focus on what to do right, instead of just pointing out bad designs.
This makes the book inspiring instead of shaming.

💼 Real-Life Example from My Previous Job

🚧 Problem:
At my previous job, we had an internal pipeline management tool used by fewer than 500 employees. Onboarding new users was challenging because we had to constantly update the documentation with each new feature, causing confusion and inefficiencies.

🔧 Solution:
We were given the green light to rethink the process, and without realising it at the time, we instinctively applied the “Don’t make me think” principle — we simplified the interface. We removed redundant steps, displayed only relevant options based on the user’s department, and included all necessary information directly within the form, so users didn’t have to visit additional pages.

📈 Benefit:
The average time users spent on a form dropped from 4 minutes to 1 minute. Additionally, because all the relevant information was embedded in the form itself, we no longer had to manage constantly updating documentation, solving the original issue of keeping it current with new features. The result was a more efficient tool and a smoother user experience.

📋 Ready-to-Use: Usability Audit Checklist

Want a quick win? Run this checklist on your website today:

✅ Can users tell what the page is about in 5 seconds?
✅ Is the main navigation instantly visible?
✅ Do all buttons clearly say what they do?
✅ Is the text scannable (short, clear, bolded keywords)?
✅ Did you remove unnecessary choices?

📖 Final Verdict: Read This Book

If you design, code, or manage websites — read this book.👓

Then, use the checklist to audit your site today.🧐

💬 Join the Conversation

What usability mistakes frustrate you the most?
📚 Got any other must-read books for developers?
👉 Comment directly on this LinkedIn post and let’s discuss!