Don't Make Me Think: A Common Sense Approach to Web Usability
The most widely sold web usability book ever written, and it earns the distinction by being short, funny, and relentlessly practical.
Krug's central argument is that users do not read pages — they scan them, and every element that requires thought is a cost the designer chose to impose.
The book demolished the then-common practice of debating design decisions through opinion by demonstrating that a morning of hallway usability testing reveals more than a month of meetings.
Its lasting contribution is not any specific guideline but the attitude it instilled: usability testing can be fast, cheap, and informal, so there is no excuse for not doing it.
Twenty-five years later, many teams still do not test with real users, which makes this book's argument as urgent as it was in 2000.
Central argument
Krug argues that good web design requires zero cognitive load: users do not read interfaces, they scan them, and any element that forces a decision or interpretation is a design failure. His central thesis is captured in the title itself — the best interfaces are self-evident, not merely self-explanatory. Beyond interface heuristics, Krug makes a methodological argument that may be more durable: a few hours of informal hallway usability testing with real users consistently outperforms lengthy internal design debates driven by competing opinions.
Critique
The book's greatest strength — its insistence on simplicity and scanning behavior — doubles as its blind spot: it was written for an era of static informational websites, and its framework struggles to account for interfaces where complexity is intrinsic to the value proposition, such as professional tools, data-dense dashboards, or multi-step transactional flows where cognitive engagement is not a failure but a feature. Krug's usability testing methodology is also deliberately kept shallow — quick hallway sessions are excellent for catching obvious friction but poorly suited to surfacing systemic problems in task completion, mental model mismatches, or long-term learnability.
Why it matters for product
For a CPO, the book's most operationally useful argument is the one about testing cadence: if usability testing can be done informally in a morning, then any product organization that ships features without user observation is making a resourcing choice, not facing a structural constraint. This reframes a common discovery failure — 'we don't have time to test' — as a prioritization failure, which is a conversation a product leader is better positioned to have than a researcher. It also provides a clear standard for design reviews: instead of arbitrating opinions, teams can ask whether the interface requires thought, and test to find out.