Don't Make Me Think

About the book

Don't Make Me Think is Steve Krug's compact handbook on making websites easier to use. Krug writes for people who build or commission web pages rather than for specialists in human-computer interaction. His central argument is simple to state and harder to practice: a page should explain itself, so visitors spend their attention on their goal instead of on decoding the interface.

The book works through the habits that cause trouble, such as ambiguous labels, cluttered layouts and navigation that hides its logic. Krug favors plain language, obvious links and designs that survive a quick glance. He also describes lightweight usability testing, in which a handful of ordinary users attempt real tasks while someone watches. The method is deliberately cheap and informal, meant to fit inside ordinary project schedules rather than replace them.

Krug's tone is conversational and often funny, with illustrations carrying much of the argument. The result reads less like a textbook than a set of working opinions from someone who has watched many people struggle with screens. That directness is the book's appeal and also the reason to read it with a pencil nearby.

How to read it

Read the early chapters as a diagnosis before treating the later material as a checklist. Krug builds a case about how people actually scan pages, then applies it. If a recommendation seems arbitrary, trace it back to the behavior it addresses. The illustrations reward slow attention; they often make a point faster than the surrounding text.

The book is short and can be finished in an evening, but its advice lands better when tested against a real page. Keep a current site or prototype open and ask whether each principle holds there. Pay attention to where Krug's examples date from; web conventions have shifted, and some interface fashions in the book now look old even where the underlying reasoning still applies.

Who it suits

Designers, developers, product managers and writers who shape web pages will find useful vocabulary here, especially anyone who needs to justify simple choices to colleagues who prefer decoration. People commissioning a site without a technical background will get a clear sense of what to ask for. Students meeting usability for the first time get a friendly entry point that avoids jargon.

Reading considerations

This is a book about general principles, not a current technical manual. Interface conventions, device sizes and accessibility expectations have moved on since the first edition, so check which edition you hold and treat specific examples as historical. The informal testing approach is a starting point, not a substitute for rigorous research or for legal accessibility requirements. Readers seeking depth on cognition or statistics should look elsewhere.