Key Takeaways
Remove tiny puzzles before they drain a visitor's attention
Make the purpose obvious. Usability means helping people accomplish a task without unnecessary confusion or frustration. A visitor should be able to tell what a page is for and how to proceed with little effort. Familiar labels such as Jobs or Search usually work better than clever names that need decoding. Clickable elements should look clickable, too. Each small uncertainty may seem harmless, but several can make a site feel tiring and unreliable.
Aim for clear, not simplistic. Some unusual or complicated pages cannot explain themselves instantly. They should still provide enough cues, layout, and concise text to make their purpose understandable after a brief look. The goal is not to remove every challenge from the task. It is to stop the interface from adding challenges of its own.
What's useful here is the distinction between effort spent on the task and effort spent interpreting the tool. Cognitive psychology describes limited working memory: when attention is consumed by unclear labels or uncertain controls, less remains for the user's actual goal. Clarity is therefore not merely a matter of taste. It is a way to protect attention. The principle has a boundary, though. Some tasks require judgment, exploration, or learning. A design should reduce accidental confusion without pretending that every meaningful decision can be made effortless.
Build for scanning, quick guesses, and imperfect understanding
Design for actual behavior. People usually scan web pages rather than read them closely. They are often in a hurry, care about only a fraction of the page, and look for words related to their immediate goal. They also tend to choose the first plausible link, a strategy called satisficing, rather than compare every option. If the guess fails, going back is usually cheap.
Expect improvised use. Visitors often get things done without understanding how a site works. Krug describes people repeatedly entering a site's address into a search engine, apparently treating the search page as their route to the Web. That behavior may be inefficient, but it is a clue about the user's mental model. Clear pages help people find more of what they need and make fewer wrong turns.
This account aligns with bounded rationality: people make workable decisions with limited time and information rather than calculating an ideal choice. That behavior is not necessarily careless; it is often an efficient response to low stakes and easy recovery. It also has limits. When a wrong click carries serious consequences, such as submitting a payment or deleting information, the interface should encourage verification rather than reward speed. Good design matches the user's likely strategy to the cost of being wrong.
Use visual hierarchy and familiar conventions to make meaning visible
Let appearance explain structure. A visual hierarchy uses size, position, spacing, and grouping to show what matters, what belongs together, and what sits inside a larger section. A clear hierarchy lets visitors grasp a page before reading every word. Newspapers use the same logic: prominent headlines and grouped stories signal importance and relationships.
Borrow patterns people know. Familiar conventions, such as a recognizable search box or shopping cart, reduce the need to learn each site from scratch. Make links and buttons visibly interactive, divide pages into distinct areas, and remove decorative clutter that competes with useful content. Invent a new pattern only when it is at least as clear as the one it replaces or offers enough value to justify learning it.
The insight connects to perceptual grouping: people rapidly infer relationships from proximity, similarity, and contrast, often before they consciously read labels. Conventions act like shared visual vocabulary, making the interface legible across contexts. This also explains why an unconventional design can look elegant to its maker yet remain opaque to a first-time visitor. Familiarity is not an absolute virtue, however. A convention can preserve a poor interaction. The sensible test is not whether a pattern is traditional, but whether users can recognize and use it reliably.
Simplify choices, labels, and copy before adding instructions
Make each decision easy. The number of clicks matters less than the uncertainty involved in each one. A visitor may gladly follow several clear steps but hesitate over a single choice with ambiguous labels. A straightforward category question is easier than asking people to decode internal product names or decide whether they belong under Home or Office.
Cut text that blocks the task. Krug argues for sharply reducing nonessential copy, especially welcoming chatter and lengthy instructions. In one example, a survey introduction was shortened from 103 words to 41. The shorter version surfaced the few facts visitors needed. If people cannot use a page without a paragraph of directions, first consider whether its labels or layout can do that work instead.
This is a practical form of choice architecture: the way options are presented can make a decision feel obvious or needlessly taxing. It also reflects progressive disclosure, the idea of showing detail when it becomes relevant instead of placing every option up front. But brevity is not automatically clarity. Legal, financial, medical, and privacy decisions may require fuller explanation. The useful standard is not fewer words at any cost; it is the smallest amount of language that lets a person make an informed choice.
Treat navigation as a map for people dropped anywhere
Give visitors their bearings. In a physical store, signs and aisles reveal where a person is and what choices lie ahead. A website offers fewer cues: pages can appear instantly, without a sense of distance or direction, and visitors may arrive through a search result deep inside the site. Navigation must supply the missing map.
Check every page with the trunk test. Pick a page at random, look at it briefly, and see whether a newcomer can identify the site, page, major sections, local choices, current location, and search. Persistent navigation keeps key controls in familiar places; page names should match the links that brought people there. Breadcrumbs can show a route back, but they work best alongside navigation that reveals the site's broader structure.
The map metaphor captures an important difference between online and physical space: digital pages provide little ambient evidence of location. Consistent navigation reduces the need to remember how a visitor arrived and makes recovery possible after a mistaken turn. The trunk test is especially useful because it tests the page as an isolated landing point, not as one step in an ideal journey. Still, navigation cannot compensate for confusing categories or broken search. A map is only useful when its landmarks match the territory.
Make the home page explain the site and its first step
Answer the visitor's first questions. A home page has to identify the site, explain its purpose, show what it offers, and make clear where to begin. A concise tagline near the site name and a short introductory statement can clarify the value of an unfamiliar service. A polished mission statement often fails because it describes the organization in grand terms without telling visitors what they can do.
Protect the page from overload. Every team wants a prominent link, but each addition makes the central message harder to see. Krug compares this pressure to a shared pasture: each group benefits from adding its own promotion while everyone bears the cost of clutter. Make room for the essential entry points, and use other pages or rotating placements for competing promotions.
The home page is a scarce attention resource as well as a design surface. Its internal politics resemble a commons problem: local teams gain from extra visibility, while the shared experience deteriorates gradually. Clear ownership and explicit priorities can prevent the familiar cycle of adding one more banner. The home page is not every visitor's landing page, particularly when search engines send people directly to deeper content. That makes page-level context important too, but it does not remove the home page's job of orienting first-time visitors.
Test three people early, then fix what repeatedly blocks them
Keep testing small and frequent. A usability test means watching one person try to understand or use a site while a facilitator observes. Krug recommends three or four people per round, rather than postponing tests until a large, expensive study can be arranged. Begin with comparable sites, sketches, and rough prototypes, then test working pages and repeat after changes. Testing early leaves time to act on what people reveal.
Look for useful evidence, not perfection. A focus group gathers opinions through group discussion; it does not show whether someone can complete a task. In a usability test, observe what people do. Triage the serious blocks first, distinguish them from brief wrong turns users recover from, and avoid treating every request for a new feature as a necessary fix.
Small rounds are a strong fit for formative design: their purpose is to expose problems early, not estimate how common each problem is across a population. This distinction helps prevent a handful of observations from being mistaken for statistical proof. The approach also lowers the cost of learning, so a team can compare successive versions rather than defend a single polished launch. The sample still matters when users have specialized knowledge or sharply different needs. In those cases, small tests should include those distinct groups at least once.
Replace opinion battles with evidence from actual use
Stop designing for an imaginary average. Team members often mistake their own preferences for what most visitors want. Designers may favor visual polish, developers may prize features, and business leaders may push for prominent promotions. These perspectives can produce circular arguments because preferences alone cannot settle whether a specific design works for a particular audience.
Ask a testable question. Instead of debating whether drop-down menus are good in general, build the proposed menu and watch likely visitors use it in context. Testing cannot prove that one approach is universally best. It gives the team direct evidence about where people hesitate, misread labels, or fail to complete a task. Watching even one test can also help stakeholders see the site through someone else's eyes.
The shift is from debating abstractions to observing situated behavior, a move common to good empirical practice. People may dislike a feature in the abstract yet use a restrained version successfully, or praise an attractive mock-up that confuses them in practice. Context therefore matters more than categorical opinions. Testing is not a substitute for expertise: participants reveal friction, while the team still has to interpret causes, weigh trade-offs, and choose remedies. Used well, observation makes disagreement more specific and productive.
Earn trust by respecting users' time, privacy, and errors
Treat goodwill as finite. Krug describes a goodwill reservoir that shrinks when a site hides important information, asks for unnecessary personal details, or makes visitors jump through avoidable hoops. An airline site that ignored an imminent labor dispute, for example, failed to answer the urgent question ticket holders came to ask. The omission damaged confidence more than a plain, candid update would have.
Show consideration in the details. Make common tasks easy, disclose costs, accept familiar data formats, and offer clear recovery from errors. Ask only for information needed for the current exchange. Extra form fields can discourage completion and encourage false answers. Promotional animation or visual spectacle may be a deliberate business choice, but teams should understand the cost to the visitor rather than assume that more excitement is always better.
Goodwill is a useful way to think about trust as a series of interactions rather than a brand asset that marketing can manufacture. Privacy research often describes a tension between the value people receive and the information they disclose; unnecessary questions shift that balance toward suspicion. Candor can preserve credibility even when the news is bad. The metaphor has limits: a visitor's patience varies with urgency, past experience, and the importance of the task. A site cannot count on a uniform reserve of tolerance.
Build accessibility into ordinary design, not as a late compliance task
Make the site work for more people. Accessibility is part of usability because people with disabilities are part of the audience. Blind visitors using screen readers scan by listening, moving quickly among headings and links rather than hearing every word. A page that is confusing to sighted visitors is unlikely to become clearer when its content is encountered through speech.
Start with high-impact practices. Test confusing pages, provide useful text alternatives for images, connect form labels to their fields, make all content usable by keyboard, and offer a way to skip repeated navigation. Cascading Style Sheets separate content order from visual presentation and allow text resizing. Automated checkers can catch some mistakes, but they cannot determine whether the experience makes sense to a person.
Accessibility is strongest when treated as an ordinary design constraint, not a specialized repair stage. Clear labels, predictable structure, and keyboard access often improve the experience beyond the group they were initially intended to serve. This resembles universal design, which seeks environments usable by a wide range of people without assuming a single default body or mode of interaction. Yet shared benefits should not be used to erase specific needs. Automated checks and general usability tests cannot stand in for testing with people who use assistive technologies.
Analysis
This is a practical design book, but its deeper subject is the gap between what makers imagine and what people actually do. Its method is observational: watch ordinary visitors scan, guess, recover, and muddle through, then redesign around those behaviors. That makes the book less a catalogue of interface rules than a case for intellectual humility. The user's error is often evidence about the design, not proof of the user's inadequacy.
The book's enduring strength is its attention to small frictions. A misleading label, an invisible button, or a needless form field rarely looks catastrophic in isolation. Together, such obstacles spend attention and weaken confidence. This connects interface usability to service design: every handoff, disclosure, and recovery path shapes the perceived character of the organization. A usable site communicates competence partly through what it does not demand from its visitors.
The advice to test a few people frequently is especially valuable as a way to learn, but its evidentiary role needs care. Small qualitative tests can uncover confusing labels or broken task flows; they cannot establish population-wide preferences or quantify conversion effects. Teams should treat findings as diagnostic clues, then use broader measurement when the decision requires estimates of prevalence or impact. Similarly, ease is not always the sole good. Some choices deserve friction when the user needs time to understand consequences.
The book's 2006 examples belong to an older web, yet its central problem survives every redesign of devices and conventions: creators know the system, while visitors encounter only its visible traces. That asymmetry makes clarity an ethical as well as commercial obligation. The most useful test is not whether a page looks polished to its creators, but whether a newcomer can confidently act, recover, and understand what the organization is asking of them.
Review Summary
Don't Make Me Think is praised as an essential guide to web usability, offering practical advice on creating intuitive and user-friendly websites. Readers appreciate Krug's straightforward writing style, humor, and use of examples. While some find the content obvious or outdated, many consider it valuable for both beginners and experienced designers. The book emphasizes simplicity, clear navigation, and user-centric design. It also covers usability testing and accessibility. Despite its age, most reviewers agree that the core principles remain relevant in modern web design.
People Also Read
Glossary
Satisficing
Choosing the first workable optionA decision strategy in which someone selects the first option that seems reasonable instead of comparing every possibility to find the theoretical best choice. On websites, people often click the first link that appears likely to match their goal. The strategy is efficient when choices are low risk and mistakes are easy to undo.
Persistent navigation
Navigation repeated across pagesThe set of navigation elements that appears consistently throughout a website, usually in the same position and visual style. It can include the site identity, links to major sections, utilities, and search. Consistency helps visitors recognize the site, find familiar controls, and regain their bearings when they arrive on an unfamiliar page.
Breadcrumbs
A trail through page levelsA navigation aid that displays the path from a site's home page through the hierarchy to the current page. Breadcrumbs let visitors move back to a broader level and see how the current page fits into that path. They are most useful as a supplement to navigation that also makes the site's wider structure visible.
Trunk test
A quick navigation clarity checkA way to assess a web page as if a visitor had been dropped onto it without context. Look briefly at a random page and check whether the site identity, page name, major sections, local options, current location, and search are easy to find. The test reveals whether navigation works beyond a carefully planned route from the home page.
Kayak problems
Brief, recoverable wrong turnsMinor usability problems in which visitors make an incorrect choice but quickly recognize the mistake and recover without help. Krug suggests prioritizing problems that cause lasting confusion or prevent task completion over these harmless detours. If a wrong turn is easy to recover from and does not appear to frustrate users, it may not merit immediate redesign.
Goodwill reservoir
A visitor's limited patienceA metaphor for the patience and trust a visitor brings to a site. Confusing design, hidden costs, unnecessary questions, and poor error recovery reduce that reserve; clear information and considerate treatment can restore it. The reserve differs among people and situations, so a site should not assume visitors will tolerate repeated obstacles.
Cubicle tests
Informal checks of page clarityQuick, informal usability checks in which a team member shows a newly created page, often a form, to a nearby colleague and asks whether it makes sense. These checks can catch obvious problems with labels, layout, and instructions before formal testing. They do not replace observing representative visitors, but they make early feedback easy to obtain.
FAQ
What's "Don't Make Me Think" about?
- Web Usability Focus: "Don't Make Me Think" by Steve Krug is a guide to web usability, emphasizing the importance of intuitive design that doesn't require users to think too much.
- Practical Advice: The book provides practical advice on how to create user-friendly websites by focusing on design principles rather than technology.
- User-Centric Approach: It stresses the importance of understanding how users interact with websites and designing with their needs in mind.
- Second Edition Updates: The second edition includes updated examples and additional chapters on accessibility and usability testing.
Why should I read "Don't Make Me Think"?
- Improve Usability Skills: It offers valuable insights into making websites more user-friendly, which is crucial for anyone involved in web design or development.
- Practical and Concise: The book is known for its brevity and practical approach, making it easy to read and apply the concepts quickly.
- Widely Respected: Steve Krug is a respected figure in the field of usability, and his book is considered a classic in web design literature.
- Broad Audience: Whether you're a designer, developer, or project manager, the book provides relevant advice for improving web usability.
What are the key takeaways of "Don't Make Me Think"?
- First Law of Usability: Krug's first law is "Don't make me think," emphasizing that web pages should be self-evident and intuitive.
- User Behavior Insights: Users scan pages rather than read them, and they often satisfice, choosing the first reasonable option rather than the best one.
- Importance of Testing: Regular usability testing is crucial, even if it's informal and involves just a few users.
- Clear Navigation: Effective navigation is essential for a good user experience, and it should be consistent and easy to understand.
How does Steve Krug define usability in "Don't Make Me Think"?
- Ease of Use: Usability means ensuring that a person of average ability can use a website for its intended purpose without frustration.
- Common Sense Approach: Krug advocates for a common-sense approach to usability, focusing on making things obvious and self-explanatory.
- User-Centric Design: The design should prioritize the user's needs and minimize the cognitive load required to navigate the site.
- Iterative Testing: Usability is best achieved through iterative testing and refinement based on user feedback.
What is Krug's First Law of Usability?
- "Don't Make Me Think": The first law is that web pages should be self-evident, meaning users should understand them without having to think.
- Obvious and Intuitive: The design should be obvious and intuitive, allowing users to navigate without confusion or hesitation.
- Reduce Cognitive Load: By minimizing the cognitive load, users can focus on their tasks rather than figuring out how to use the site.
- Ultimate Tie Breaker: This principle serves as the ultimate tie breaker when deciding if a design works or not.
What are some best practices for web navigation according to "Don't Make Me Think"?
- Consistent Navigation: Use persistent navigation elements that appear on every page to provide a consistent user experience.
- Clear Visual Hierarchy: Create a clear visual hierarchy to help users understand the relationships between different elements on a page.
- Use Conventions: Take advantage of web conventions to make navigation intuitive and reduce the learning curve for users.
- Highlight Current Location: Use "You are here" indicators to show users their current location within the site.
How does Krug suggest handling usability testing?
- Start Early and Test Often: Begin testing early in the design process and continue testing iteratively to catch issues before they become ingrained.
- Simple and Inexpensive: Usability testing doesn't have to be expensive or complicated; even testing with a few users can provide valuable insights.
- Focus on Key Tasks: Test key tasks that users are likely to perform on the site to ensure they can complete them easily.
- Observe and Adjust: Watch users interact with the site, note where they struggle, and make adjustments based on these observations.
What role do taglines play in web design according to "Don't Make Me Think"?
- Convey Site Purpose: Taglines should clearly convey the purpose of the site and what makes it unique or valuable.
- Positioning: They are typically placed near the Site ID to immediately inform users about the site's mission.
- Brevity and Clarity: Effective taglines are concise, usually six to eight words, and provide a clear benefit or differentiation.
- Avoid Jargon: Taglines should avoid vague or generic language that doesn't add value or clarity.
What are some common usability issues highlighted in "Don't Make Me Think"?
- Unclear Navigation: Users often struggle with navigation that isn't intuitive or consistent across the site.
- Excessive Text: Pages with too much text can overwhelm users; Krug advises cutting unnecessary words.
- Hidden Information: Important information, like contact details or pricing, should not be hidden or difficult to find.
- Complex Forms: Forms should be simple and only ask for necessary information to avoid user frustration.
How does Krug address accessibility in "Don't Make Me Think"?
- Part of Usability: Accessibility is an integral part of usability, ensuring that all users, including those with disabilities, can use the site.
- Simple Adjustments: Implementing basic accessibility features, like alt text for images and keyboard navigation, can significantly improve usability.
- Cascading Style Sheets (CSS): Using CSS can help create accessible designs by allowing for flexible layouts and text resizing.
- Right Thing to Do: Beyond legal requirements, making a site accessible is the right thing to do as it can dramatically improve some users' lives.
What are some of the best quotes from "Don't Make Me Think" and what do they mean?
- "Don't make me think!": This quote encapsulates the book's core message that web design should be intuitive and self-evident.
- "Get rid of half the words on each page, then get rid of half of what's left.": This emphasizes the importance of concise content that doesn't overwhelm users.
- "Usability testing on 10 cents a day.": Krug highlights that usability testing can be simple and inexpensive, yet highly effective.
- "The Farmer and the Cowman Should Be Friends.": This chapter title suggests that different stakeholders in web design should collaborate despite differing perspectives.
How does "Don't Make Me Think" address the balance between design and functionality?
- Design for Users: The book stresses that design should prioritize user needs and ease of use over aesthetic appeal alone.
- Avoid Over-Design: While visual appeal is important, it should not come at the expense of functionality or user experience.
- Iterative Improvement: Design should be refined through iterative testing and feedback to ensure it meets user needs effectively.
- Balance Sizzle and Substance: Krug advises against adding unnecessary "sizzle" that can detract from the site's usability and purpose.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.