Plot Summary

Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability (voices That Matter)

Steve Krug
Guide cover placeholder

Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability (voices That Matter)

Nonfiction | Book | Adult | Published in 2000

Plot Summary

The third edition of this widely influential guide to web usability updates the original with new examples and a chapter on mobile design. Steve Krug, a usability consultant whose work involves reviewing designs and watching people try to use products, explains that while the technology landscape has changed dramatically, the core principles remain the same because usability is about how people think and behave, not about technology. Usability has gone mainstream under the broader umbrella of User Experience Design (UX), but many practitioners remain uncertain about what to do in practice. Krug writes for designers, developers, project managers, and others who must handle usability themselves, keeping the book deliberately short. He defines usability simply: A person of average or below-average ability and experience can figure out how to use something to accomplish a task without it being more trouble than it's worth.

Krug opens with his First Law of Usability: "Don't make me think." Web pages should be self-evident, requiring no effort to understand. Common sources of unnecessary thinking include clever or obscure labels, links that do not look clickable, and input fields that behave unpredictably. He contrasts two flight-booking sites: one produces confusion through ambiguous fields and unhelpful error messages, while the other eliminates confusion with smart suggestions that anticipate user intent. Every question mark adds to cognitive workload and erodes confidence in the site.

He then presents three "facts of life" about how people actually use the web. First, people do not read pages; they scan them, looking for relevant words much as they scan newspapers or social media feeds. Second, people "satisfice," choosing the first reasonable option rather than the best one. Drawing on Gary Klein's research into how firefighters and other professionals decide under pressure, Krug explains that web users follow the same pattern because the penalty for guessing wrong is just a click of the Back button. Third, people do not figure out how things work; they muddle through, often unable even to describe what a web browser is. Since users treat pages like billboards glimpsed at high speed, designers should design accordingly.

Krug lays out six strategies for designing scannable pages. Conventions, or standardized design patterns like placing a logo in the upper-left corner, reduce the thinking users must do. He advises innovating only when designers have a genuinely better idea and introduces the principle that clarity trumps consistency. Effective visual hierarchies make important elements prominent, group related items, and nest sub-items within parent elements. Pages should be divided into clearly defined areas, and clickable elements must be visually distinct. He identifies three kinds of visual noise: pages where everything shouts for attention, disorganized layouts, and excessive clutter. For text, he advises plenty of headings, short paragraphs, bulleted lists, and bolded key terms.

His Second Law holds that what matters is not how many clicks it takes to reach content but how much thought each click requires: Three mindless, unambiguous clicks equal one click that requires thought. When difficult choices are unavoidable, designers should provide guidance that is brief, timely, and impossible to miss, citing London's "LOOK RIGHT" signs painted at street crossings as an ideal example of just-in-time guidance.

His Third Law states that designers should eliminate half the words on every page, then half of what remains. He targets "happy talk," the self-congratulatory introductory text that conveys no useful information, and instructions that no one reads until muddling through has failed.

Krug devotes an extended chapter to navigation, using the analogy of shopping at a department store to illustrate how physical wayfinding maps onto the web. Key differences make web navigation critical: online, users have no sense of scale, direction, or location. Navigation is not merely a feature; it essentially is the website. Persistent navigation, the set of links that appears on every page, should include a Site ID or logo, primary sections, utility links, and a search box. Every page needs a prominent name matching what the user clicked, and "You are here" indicators must register at a glance. He advocates for breadcrumbs, a trail of links showing the page's place in the site hierarchy. He also introduces the "trunk test": imagining being dropped onto any page and checking whether you can immediately identify the Site ID, page name, sections, local navigation (links to pages within the current section), your current location, and how to search.

Turning to Home page design, Krug introduces the "Big Bang Theory of Web Design": users' first few seconds on a page are critical because snap judgments tend to predict later assessments. The Home page must quickly answer what the site is, what it offers, what users can do, and why they should stay. Three places to communicate purpose are the tagline near the logo, a terse Welcome blurb, and a short explanatory video. He warns against the "tragedy of the commons," where each stakeholder's promotion collectively overloads the page.

Krug argues that most team debates about usability are unproductive "religious debates" driven by members projecting their own preferences onto users. He dismantles the myth of the Average User, arguing that all web use is idiosyncratic. Only usability testing can determine whether a specific implementation creates a good experience.

He presents a streamlined approach to do-it-yourself testing: one morning a month, three participants, with the team debriefing over lunch. He distinguishes usability tests, where individuals try to use something, from focus groups, where people discuss opinions. Testing one user is 100 percent better than testing none, and testing early outweighs testing extensively at the end. He advises recruiting participants loosely, since most serious problems trouble almost anyone. During debriefing, the team ranks problems, assigns fixes, and stops once available resources are committed.

Addressing mobile usability, Krug notes that for many people in emerging countries the smartphone is their first and only computer. The basic principles hold, but smaller screens create difficult tradeoffs. He warns that flat design, a minimalist style that removes depth cues like raised buttons and bordered fields, can obscure which elements are interactive, and that touch screens eliminate hover functionality. He discusses the usability attributes of delight, learnability, and memorability.

Krug frames usability as common courtesy, introducing a "reservoir of goodwill" that users bring to every visit. Each frustration depletes this reservoir, from hidden support phone numbers to unnecessary data requirements. Making common tasks easy, being upfront about costs, and maintaining honest FAQ lists can refill it.

He addresses accessibility, arguing the most compelling reason to make sites accessible is that it is the right thing to do. He recommends fixing usability problems that confuse all users, studying how screen-reader users navigate (they scan with their ears, listening to just enough of each element to decide whether to continue), and implementing basics like alt text (brief image descriptions read by screen readers), proper heading structure, keyboard accessibility, and sufficient text-background contrast.

The book closes with advice for advocating usability within organizations, including getting executives to observe a usability test and testing competitor sites. Krug warns against co-opting usability to manipulate users through deceptive practices. He ends with definitive rules: never use small, low-contrast type; do not put labels inside form fields, with narrow exceptions; preserve the distinction between visited and unvisited links; and do not let headings float between paragraphs.

We’re just getting started

Add this title to our list of requested Study Guides!