Don't Make Me Think — Start Here
People don't carefully study a website, an app, a form, or a set of instructions — they skim, guess, and click on the first plausible option, moving on the instant something works well enough. Designing for that reality means removing anything that forces a moment of hesitation or confusion, testing with a small number of real users early and often, and fixing the most obvious point of confusion first rather than debating the most theoretically ideal design.
The whole book, in one line
People don't carefully study a website, an app, a form, or a set of instructions — they skim, guess, and click on the first plausible option, moving on the instant something works well enough. Designing for that reality means removing anything that forces a moment of hesitation or confusion, testing with a small number of real users early and often, and fixing the most obvious point of confusion first rather than debating the most theoretically ideal design.
How the mechanism works
The source's own progression (design so nothing requires real thought, remove unnecessary words and choices, test early with a small number of real users, and fix the most glaring problem first) maps onto four clusters with light compression, translated away from the source's own named real-website examples (see safeguards):
- Design so using it never requires real thought — if someone has to pause and figure out what a button, label, or instruction means, that half-second of hesitation is a design failure, even if they eventually work it out.
- Cut unnecessary words and choices ruthlessly — every extra sentence of explanation or extra option on a page is something a person has to read and evaluate before they can act, and most of it can simply be removed without losing anything they needed.
- Test with a small number of real people early and often, not once at the end — watching even three or four people actually try to use something surfaces more real problems than any amount of internal debate about what "should" be intuitive.
- Fix the most glaring problem before polishing anything else — a single framing paragraph: when multiple things are confusing at once, fixing the worst offender first and re-testing beats trying to perfect every detail simultaneously, since the biggest problem is usually hiding smaller ones from view entirely.
Framework fidelity: 8. The source's own clean, practical progression maps onto four clusters with only light compression; its many specific real-website screenshots and named companies are excluded and replaced with original composites, a direct but modest cost of the safety-first translation.
Who this was written for
Someone responsible for a website, app, form, or set of instructions who has watched real users struggle with something the whole internal team assumed was obvious, and wants a practical way to make things easier to use without endless debate.
Safeguards
- Real-website and real-company exclusion (critical for this title). The source illustrates its points with numerous named real websites, apps, and companies; none of these are reproduced anywhere. Every "Where this breaks" scene uses an original, invented interface, form, or product.
- No edition names the author's specific consulting business, workshop, or certification offering.
- Real named individuals and case studies from the source are never reproduced; every scene is an original composite.
- No fabricated statistics.
- No edition claims that following this package guarantees any specific usability or business outcome.
- Steve Krug named only in the title and each edition's closing line.
Cross-book vocabulary check
This is the 1st title in the new Product Design and User Experience category. No prior category has covered usability/interface design, so no cross-book check against an existing category applies yet; a same-category check will run once all five titles are drafted.
Cross-book note
This is the 1st of 5 titles opening the Product Design and User Experience category.