Design
Don't Make Me Think
by Steve Krug
Don't Make Me Think summary
Don't Make Me Think by Steve Krug is a design book whose central concern is this: Krug's practical guide argues that users usually scan pages, satisfice rather than optimize, and muddle through interfaces. Designers should therefore make navigation self-evident, remove needless words, clarify hierarchy, and test early with a small number of real users. The book develops that concern through a set of linked ideas rather than a single trick. Among its most important concepts are Don't make me think, Scanning, not reading, Satisficing, Clear visual hierarchy, along with several supporting distinctions that explain how the argument can be used in real decisions.
A strong reading also keeps the book's limits visible. No management, psychology, finance, design, or productivity framework works independently of context. The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. For Booknomics, the goal is therefore not to turn the book into a set of motivational slogans, but to explain what the author is arguing, how the ideas connect, where the framework is useful, and where the reader should remain cautious.
Detailed summary
Don't Make Me Think — Premium Deep Summary
Overview
Don't Make Me Think by Steve Krug is a design book whose central concern is this: Krug's practical guide argues that users usually scan pages, satisfice rather than optimize, and muddle through interfaces. Designers should therefore make navigation self-evident, remove needless words, clarify hierarchy, and test early with a small number of real users. The book develops that concern through a set of linked ideas rather than a single trick. Among its most important concepts are Don't make me think, Scanning, not reading, Satisficing, Clear visual hierarchy, along with several supporting distinctions that explain how the argument can be used in real decisions.
A strong reading also keeps the book's limits visible. No management, psychology, finance, design, or productivity framework works independently of context. The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. For Booknomics, the goal is therefore not to turn the book into a set of motivational slogans, but to explain what the author is arguing, how the ideas connect, where the framework is useful, and where the reader should remain cautious.
Critical synthesis
The book's core problem
Steve Krug uses Don't Make Me Think to examine a recurring problem: Krug's practical guide argues that users usually scan pages, satisfice rather than optimize, and muddle through interfaces. Designers should therefore make navigation self-evident, remove needless words, clarify hierarchy, and test early with a small number of real users. The major ideas—particularly Don't make me think, Scanning, not reading, and Satisficing—work together to explain why sensible people and organizations can still repeat patterns that undermine their stated goals.
The practical movement in Don't Make Me Think is from explanation to intervention. Don't Make Me Think does not stop at “try harder”; it points toward changes in rules, routines, expectations, attention, decision criteria, or surrounding conditions. That matters because repeated outcomes usually come from repeated structures. If the structure described by Don't Make Me Think remains unchanged, intention has to fight the same battle again.
The book is strongest when paired with restraint. The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. A responsible reader of Don't Make Me Think can therefore ask three questions throughout: what does this concept illuminate, what does it leave out, and what evidence would justify a different approach?
The framework in detail
Don't make me think
Every unexplained label, ambiguous control, or hidden convention creates cognitive work that competes with the user's goal. The analytical value of Don't make me think is that it turns a vague problem into a more observable one. Under Don't make me think, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Don't make me think, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Don't make me think, the reader needs an operational definition. What behavior would change if the idea were taken seriously? What warning sign would appear before the old problem repeats? What result would justify keeping the intervention? The next idea, Scanning, not reading, adds another constraint that prevents Don't make me think from being used too narrowly. For Don't make me think, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
Scanning, not reading
People commonly scan for words and shapes that match their purpose rather than reading a page line by line. Within Don't Make Me Think, Scanning, not reading changes the unit of attention. Scanning, not reading asks the reader to look beneath a visible result and identify the process that keeps regenerating it. Scanning, not reading matters because recurring problems are often repaired at the level of intention even when the stronger cause sits in a default routine, measurement system, incentive, environment, or social expectation.
Scanning, not reading also contains a trade-off. Emphasizing it too strongly can make another legitimate consideration less visible. Its relationship with Don't make me think is especially important: Don't make me think explains part of the setup, while Scanning, not reading changes what happens next. A good application therefore includes a review point. If using Scanning, not reading improves one outcome while quietly damaging another, the reader should adapt the tactic instead of defending the framework mechanically.
Satisficing
Users often choose the first plausible option rather than systematically comparing every route. Satisficing becomes practical when it is converted into a decision rule: what should be noticed before the situation occurs, what response should be preferred, and what evidence should be collected afterward? Using Satisficing in this way creates a learning loop in which an idea guides action, action produces information, and information refines the next decision.
That loop is central to Don't Make Me Think. Agreement with Satisficing is not implementation; the idea has to alter a real choice, process, or constraint. Scanning, not reading may explain why the old pattern exists, while Satisficing supplies a different response. The following idea, Clear visual hierarchy, broadens the response so it is less dependent on one tactic. That makes Satisficing testable: keep what improves the system, revise what does not, and separate useful evidence from loyalty to the terminology.
Clear visual hierarchy
Size, grouping, contrast, and placement should communicate what belongs together and what is most important. The analytical value of Clear visual hierarchy is that it turns a vague problem into a more observable one. Under Clear visual hierarchy, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Clear visual hierarchy, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Clear visual hierarchy, the reader needs an operational definition. What behavior would change if the idea were taken seriously? What warning sign would appear before the old problem repeats? What result would justify keeping the intervention? The next idea, Obvious navigation, adds another constraint that prevents Clear visual hierarchy from being used too narrowly. For Clear visual hierarchy, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
Obvious navigation
Users should know where they are, what the major sections are, and how to get back. Within Don't Make Me Think, Obvious navigation changes the unit of attention. Obvious navigation asks the reader to look beneath a visible result and identify the process that keeps regenerating it. Obvious navigation matters because recurring problems are often repaired at the level of intention even when the stronger cause sits in a default routine, measurement system, incentive, environment, or social expectation.
Obvious navigation also contains a trade-off. Emphasizing it too strongly can make another legitimate consideration less visible. Its relationship with Clear visual hierarchy is especially important: Clear visual hierarchy explains part of the setup, while Obvious navigation changes what happens next. A good application therefore includes a review point. If using Obvious navigation improves one outcome while quietly damaging another, the reader should adapt the tactic instead of defending the framework mechanically.
Omit needless words
Reducing instructional clutter increases the proportion of the screen devoted to useful information. Omit needless words becomes practical when it is converted into a decision rule: what should be noticed before the situation occurs, what response should be preferred, and what evidence should be collected afterward? Using Omit needless words in this way creates a learning loop in which an idea guides action, action produces information, and information refines the next decision.
That loop is central to Don't Make Me Think. Agreement with Omit needless words is not implementation; the idea has to alter a real choice, process, or constraint. Obvious navigation may explain why the old pattern exists, while Omit needless words supplies a different response. The following idea, Usability testing, broadens the response so it is less dependent on one tactic. That makes Omit needless words testable: keep what improves the system, revise what does not, and separate useful evidence from loyalty to the terminology.
Usability testing
Watching even a few people attempt realistic tasks can reveal problems that a design team has stopped noticing. The analytical value of Usability testing is that it turns a vague problem into a more observable one. Under Usability testing, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Usability testing, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Usability testing, the reader needs an operational definition. What behavior would change if the idea were taken seriously? What warning sign would appear before the old problem repeats? What result would justify keeping the intervention? As the final concept in the sequence, Usability testing also tests whether the earlier ideas form a coherent system. For Usability testing, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
How the main ideas interact
The connection between Don't make me think and Satisficing reveals how Don't Make Me Think moves from diagnosis to execution. Don't make me think changes what the reader notices or prioritizes; Satisficing changes how the response is structured. Used separately, Don't make me think can remain theoretical while Satisficing can become busy activity disconnected from the real cause.
A practical test of Don't make me think + Satisficing is to apply both to one bounded situation and review the result after a fixed period. A Don't Make Me Think review of this pair should ask whether the headline outcome improved, what new cost appeared, and whether the change depended on unrealistic effort. That feedback matters because Don't make me think + Satisficing should shape repeated decisions rather than decorate a one-time plan.
The connection between Scanning, not reading and Obvious navigation reveals how Don't Make Me Think moves from diagnosis to execution. Scanning, not reading changes what the reader notices or prioritizes; Obvious navigation changes how the response is structured. Used separately, Scanning, not reading can remain theoretical while Obvious navigation can become busy activity disconnected from the real cause.
A practical test of Scanning, not reading + Obvious navigation is to apply both to one bounded situation and review the result after a fixed period. A Don't Make Me Think review of this pair should ask whether the headline outcome improved, what new cost appeared, and whether the change depended on unrealistic effort. That feedback matters because Scanning, not reading + Obvious navigation should shape repeated decisions rather than decorate a one-time plan.
The connection between Clear visual hierarchy and Omit needless words reveals how Don't Make Me Think moves from diagnosis to execution. Clear visual hierarchy changes what the reader notices or prioritizes; Omit needless words changes how the response is structured. Used separately, Clear visual hierarchy can remain theoretical while Omit needless words can become busy activity disconnected from the real cause.
A practical test of Clear visual hierarchy + Omit needless words is to apply both to one bounded situation and review the result after a fixed period. A Don't Make Me Think review of this pair should ask whether the headline outcome improved, what new cost appeared, and whether the change depended on unrealistic effort. That feedback matters because Clear visual hierarchy + Omit needless words should shape repeated decisions rather than decorate a one-time plan.
Examples and what they are meant to show
The example of the comparison of web navigation with moving through a physical space gives Don't make me think a concrete setting. The value of the comparison of web navigation with moving through a physical space is not that every reader should copy the story, but that the story makes the mechanism behind Don't make me think visible. Through the comparison of web navigation with moving through a physical space, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring the comparison of web navigation with moving through a physical space to another context, the safe move is analogy rather than imitation. Don't Make Me Think becomes more useful when the reader checks whether the same mechanism is actually present and considers at least one alternative explanation for the outcome. This preserves the memory value of the comparison of web navigation with moving through a physical space without pretending that a vivid story proves universal causality.
The example of trunk tests that ask whether a user can identify site identity, location, navigation, and search gives Scanning, not reading a concrete setting. The value of trunk tests that ask whether a user can identify site identity, location, navigation, and search is not that every reader should copy the story, but that the story makes the mechanism behind Scanning, not reading visible. Through trunk tests that ask whether a user can identify site identity, location, navigation, and search, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring trunk tests that ask whether a user can identify site identity, location, navigation, and search to another context, the safe move is analogy rather than imitation. Don't Make Me Think becomes more useful when the reader checks whether the same mechanism is actually present and considers at least one alternative explanation for the outcome. This preserves the memory value of trunk tests that ask whether a user can identify site identity, location, navigation, and search without pretending that a vivid story proves universal causality.
The example of removing welcome text and unnecessary instructions gives Satisficing a concrete setting. The value of removing welcome text and unnecessary instructions is not that every reader should copy the story, but that the story makes the mechanism behind Satisficing visible. Through removing welcome text and unnecessary instructions, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring removing welcome text and unnecessary instructions to another context, the safe move is analogy rather than imitation. Don't Make Me Think becomes more useful when the reader checks whether the same mechanism is actually present and considers at least one alternative explanation for the outcome. This preserves the memory value of removing welcome text and unnecessary instructions without pretending that a vivid story proves universal causality.
The example of small, frequent usability tests rather than waiting for a perfect research program gives Clear visual hierarchy a concrete setting. The value of small, frequent usability tests rather than waiting for a perfect research program is not that every reader should copy the story, but that the story makes the mechanism behind Clear visual hierarchy visible. Through small, frequent usability tests rather than waiting for a perfect research program, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring small, frequent usability tests rather than waiting for a perfect research program to another context, the safe move is analogy rather than imitation. Don't Make Me Think becomes more useful when the reader checks whether the same mechanism is actually present and considers at least one alternative explanation for the outcome. This preserves the memory value of small, frequent usability tests rather than waiting for a perfect research program without pretending that a vivid story proves universal causality.
Limits and cautions
The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. This caution changes how Don't make me think should be applied. If Don't make me think moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold.
For Don't Make Me Think, responsible adaptation means lowering certainty before raising the stakes. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Don't make me think. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Don't make me think from turning into an unquestioned rule.
Some products require learning because the domain itself is complex; 'obvious' cannot mean oversimplified. This caution changes how Satisficing should be applied. If Satisficing moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold.
For Don't Make Me Think, responsible adaptation means lowering certainty before raising the stakes. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Satisficing. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Satisficing from turning into an unquestioned rule.
Accessibility and inclusive design require additional standards beyond general ease of use. This caution changes how Obvious navigation should be applied. If Obvious navigation moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold.
For Don't Make Me Think, responsible adaptation means lowering certainty before raising the stakes. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Obvious navigation. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Obvious navigation from turning into an unquestioned rule.
Deeper synthesis
The durable contribution of Don't Make Me Think comes from the sequence created by Don't make me think, Scanning, not reading, Satisficing, Clear visual hierarchy, Obvious navigation, Omit needless words, and Usability testing. In Don't Make Me Think, the early concepts sharpen diagnosis, the middle concepts alter the response, and the later concepts make that response more sustainable, measurable, or appropriately constrained. Isolating
Key ideas
Don't make me think. Every unexplained label, ambiguous control, or hidden convention creates cognitive work that competes with the user's goal. In practice, Don't make me think is useful when it changes a specific behavior, rule, or decision criterion.
Scanning, not reading. People commonly scan for words and shapes that match their purpose rather than reading a page line by line. The Booknomics takeaway is to test Scanning, not reading against an observable situation rather than accepting it only as an attractive idea.
Satisficing. Users often choose the first plausible option rather than systematically comparing every route. Used carefully, Satisficing becomes a question for action: what would be different if this principle genuinely shaped the next decision?
Clear visual hierarchy. Size, grouping, contrast, and placement should communicate what belongs together and what is most important. In practice, Clear visual hierarchy is useful when it changes a specific behavior, rule, or decision criterion.
Obvious navigation. Users should know where they are, what the major sections are, and how to get back. The Booknomics takeaway is to test Obvious navigation against an observable situation rather than accepting it only as an attractive idea.
Omit needless words. Reducing instructional clutter increases the proportion of the screen devoted to useful information. Used carefully, Omit needless words becomes a question for action: what would be different if this principle genuinely shaped the next decision?
Usability testing. Watching even a few people attempt realistic tasks can reveal problems that a design team has stopped noticing. In practice, Usability testing is useful when it changes a specific behavior, rule, or decision criterion.
Deep analysis
The book's core problem
Steve Krug uses Don't Make Me Think to examine a recurring problem: Krug's practical guide argues that users usually scan pages, satisfice rather than optimize, and muddle through interfaces. Designers should therefore make navigation self-evident, remove needless words, clarify hierarchy, and test early with a small number of real users. The major ideas—particularly Don't make me think, Scanning, not reading, and Satisficing—work together to explain why sensible people and organizations can still repeat patterns that undermine their stated goals.
The practical movement in Don't Make Me Think is from explanation to intervention. Don't Make Me Think does not stop at “try harder”; it points toward changes in rules, routines, expectations, attention, decision criteria, or surrounding conditions. That matters because repeated outcomes usually come from repeated structures. If the structure described by Don't Make Me Think remains unchanged, intention has to fight the same battle again.
The book is strongest when paired with restraint. The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. A responsible reader of Don't Make Me Think can therefore ask three questions throughout: what does this concept illuminate, what does it leave out, and what evidence would justify a different approach.
The framework in detail
Don't make me think
Every unexplained label, ambiguous control, or hidden convention creates cognitive work that competes with the user's goal. The analytical value of Don't make me think is that it turns a vague problem into a more observable one. Under Don't make me think, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Don't make me think, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Don't make me think, the reader needs an operational definition. What behavior would change if the idea were taken seriously. What warning sign would appear before the old problem repeats. What result would justify keeping the intervention. The next idea, Scanning, not reading, adds another constraint that prevents Don't make me think from being used too narrowly. For Don't make me think, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
Scanning, not reading
People commonly scan for words and shapes that match their purpose rather than reading a page line by line. Within Don't Make Me Think, Scanning, not reading changes the unit of attention. Scanning, not reading asks the reader to look beneath a visible result and identify the process that keeps regenerating it. Scanning, not reading matters because recurring problems are often repaired at the level of intention even when the stronger cause sits in a default routine, measurement system, incentive, environment, or social expectation.
Scanning, not reading also contains a trade-off. Emphasizing it too strongly can make another legitimate consideration less visible. Its relationship with Don't make me think is especially important: Don't make me think explains part of the setup, while Scanning, not reading changes what happens next. A good application therefore includes a review point. If using Scanning, not reading improves one outcome while quietly damaging another, the reader should adapt the tactic instead of defending the framework mechanically.
Satisficing
Users often choose the first plausible option rather than systematically comparing every route. Satisficing becomes practical when it is converted into a decision rule: what should be noticed before the situation occurs, what response should be preferred, and what evidence should be collected afterward. Using Satisficing in this way creates a learning loop in which an idea guides action, action produces information, and information refines the next decision.
That loop is central to Don't Make Me Think. Agreement with Satisficing is not implementation; the idea has to alter a real choice, process, or constraint. Scanning, not reading may explain why the old pattern exists, while Satisficing supplies a different response. The following idea, Clear visual hierarchy, broadens the response so it is less dependent on one tactic. That makes Satisficing testable: keep what improves the system, revise what does not, and separate useful evidence from loyalty to the terminology.
Clear visual hierarchy
Size, grouping, contrast, and placement should communicate what belongs together and what is most important. The analytical value of Clear visual hierarchy is that it turns a vague problem into a more observable one. Under Clear visual hierarchy, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Clear visual hierarchy, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Clear visual hierarchy, the reader needs an operational definition. What behavior would change if the idea were taken seriously. What result would justify keeping the intervention. The next idea, Obvious navigation, adds another constraint that prevents Clear visual hierarchy from being used too narrowly. For Clear visual hierarchy, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
Obvious navigation
Users should know where they are, what the major sections are, and how to get back. Within Don't Make Me Think, Obvious navigation changes the unit of attention. Obvious navigation asks the reader to look beneath a visible result and identify the process that keeps regenerating it. Obvious navigation matters because recurring problems are often repaired at the level of intention even when the stronger cause sits in a default routine, measurement system, incentive, environment, or social expectation.
Obvious navigation also contains a trade-off. Its relationship with Clear visual hierarchy is especially important: Clear visual hierarchy explains part of the setup, while Obvious navigation changes what happens next. A good application therefore includes a review point. If using Obvious navigation improves one outcome while quietly damaging another, the reader should adapt the tactic instead of defending the framework mechanically.
Omit needless words
Reducing instructional clutter increases the proportion of the screen devoted to useful information. Omit needless words becomes practical when it is converted into a decision rule: what should be noticed before the situation occurs, what response should be preferred, and what evidence should be collected afterward. Using Omit needless words in this way creates a learning loop in which an idea guides action, action produces information, and information refines the next decision.
That loop is central to Don't Make Me Think. Agreement with Omit needless words is not implementation; the idea has to alter a real choice, process, or constraint. Obvious navigation may explain why the old pattern exists, while Omit needless words supplies a different response. The following idea, Usability testing, broadens the response so it is less dependent on one tactic. That makes Omit needless words testable: keep what improves the system, revise what does not, and separate useful evidence from loyalty to the terminology.
Usability testing
Watching even a few people attempt realistic tasks can reveal problems that a design team has stopped noticing. The analytical value of Usability testing is that it turns a vague problem into a more observable one. Under Usability testing, the outcome is not treated only as a verdict on character or intelligence; the reader can inspect the conditions that make the pattern likely. For Usability testing, those conditions may include timing, incentives, friction, expectations, information quality, or the order in which choices occur.
To apply Usability testing, the reader needs an operational definition. What behavior would change if the idea were taken seriously. What result would justify keeping the intervention. As the final concept in the sequence, Usability testing also tests whether the earlier ideas form a coherent system. For Usability testing, translating the label into observable behavior is what makes the idea useful after the initial enthusiasm of reading has faded.
How the main ideas interact
The connection between Don't make me think and Satisficing reveals how Don't Make Me Think moves from diagnosis to execution. Don't make me think changes what the reader notices or prioritizes; Satisficing changes how the response is structured. Used separately, Don't make me think can remain theoretical while Satisficing can become busy activity disconnected from the real cause.
A practical test of Don't make me think + Satisficing is to apply both to one bounded situation and review the result after a fixed period. A Don't Make Me Think review of this pair should ask whether the headline outcome improved, what new cost appeared, and whether the change depended on unrealistic effort. That feedback matters because Don't make me think + Satisficing should shape repeated decisions rather than decorate a one-time plan.
The connection between Scanning, not reading and Obvious navigation reveals how Don't Make Me Think moves from diagnosis to execution. Scanning, not reading changes what the reader notices or prioritizes; Obvious navigation changes how the response is structured. Used separately, Scanning, not reading can remain theoretical while Obvious navigation can become busy activity disconnected from the real cause.
A practical test of Scanning, not reading + Obvious navigation is to apply both to one bounded situation and review the result after a fixed period. That feedback matters because Scanning, not reading + Obvious navigation should shape repeated decisions rather than decorate a one-time plan.
The connection between Clear visual hierarchy and Omit needless words reveals how Don't Make Me Think moves from diagnosis to execution. Clear visual hierarchy changes what the reader notices or prioritizes; Omit needless words changes how the response is structured. Used separately, Clear visual hierarchy can remain theoretical while Omit needless words can become busy activity disconnected from the real cause.
A practical test of Clear visual hierarchy + Omit needless words is to apply both to one bounded situation and review the result after a fixed period. That feedback matters because Clear visual hierarchy + Omit needless words should shape repeated decisions rather than decorate a one-time plan.
Examples and what they are meant to show
The example of the comparison of web navigation with moving through a physical space gives Don't make me think a concrete setting. The value of the comparison of web navigation with moving through a physical space is not that every reader should copy the story, but that the story makes the mechanism behind Don't make me think visible. Through the comparison of web navigation with moving through a physical space, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring the comparison of web navigation with moving through a physical space to another context, the safe move is analogy rather than imitation. Don't Make Me Think becomes more useful when the reader checks whether the same mechanism is actually present and considers at least one alternative explanation for the outcome. This preserves the memory value of the comparison of web navigation with moving through a physical space without pretending that a vivid story proves universal causality.
The example of trunk tests that ask whether a user can identify site identity, location, navigation, and search gives Scanning, not reading a concrete setting. The value of trunk tests that ask whether a user can identify site identity, location, navigation, and search is not that every reader should copy the story, but that the story makes the mechanism behind Scanning, not reading visible. Through trunk tests that ask whether a user can identify site identity, location, navigation, and search, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring trunk tests that ask whether a user can identify site identity, location, navigation, and search to another context, the safe move is analogy rather than imitation. This preserves the memory value of trunk tests that ask whether a user can identify site identity, location, navigation, and search without pretending that a vivid story proves universal causality.
The example of removing welcome text and unnecessary instructions gives Satisficing a concrete setting. The value of removing welcome text and unnecessary instructions is not that every reader should copy the story, but that the story makes the mechanism behind Satisficing visible. Through removing welcome text and unnecessary instructions, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring removing welcome text and unnecessary instructions to another context, the safe move is analogy rather than imitation. This preserves the memory value of removing welcome text and unnecessary instructions without pretending that a vivid story proves universal causality.
The example of small, frequent usability tests rather than waiting for a perfect research program gives Clear visual hierarchy a concrete setting. The value of small, frequent usability tests rather than waiting for a perfect research program is not that every reader should copy the story, but that the story makes the mechanism behind Clear visual hierarchy visible. Through small, frequent usability tests rather than waiting for a perfect research program, the reader can ask which constraint changed, what behavior became easier or harder, which incentive shifted, and what information became newly available.
When transferring small, frequent usability tests rather than waiting for a perfect research program to another context, the safe move is analogy rather than imitation. This preserves the memory value of small, frequent usability tests rather than waiting for a perfect research program without pretending that a vivid story proves universal causality.
Limits and cautions
The original examples come from earlier generations of websites, though the underlying principles remain broadly useful. This caution changes how Don't make me think should be applied. If Don't make me think moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold.
For Don't Make Me Think, responsible adaptation means lowering certainty before raising the stakes. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Don't make me think. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Don't make me think from turning into an unquestioned rule.
Some products require learning because the domain itself is complex; 'obvious' cannot mean oversimplified. This caution changes how Satisficing should be applied. If Satisficing moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Satisficing. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Satisficing from turning into an unquestioned rule.
Accessibility and inclusive design require additional standards beyond general ease of use. This caution changes how Obvious navigation should be applied. If Obvious navigation moves into a different industry, culture, income level, health situation, legal system, or power structure, the assumptions behind the original recommendation may no longer hold. Ask who bears the downside, whether the decision can be reversed, and what local evidence would contradict Obvious navigation. In Don't Make Me Think, the purpose of this caution is not to weaken the book; it is to stop Obvious navigation from turning into an unquestioned rule.
Deeper synthesis
The durable contribution of Don't Make Me Think comes from the sequence created by Don't make me think, Scanning, not reading, Satisficing, Clear visual hierarchy, Obvious navigation, Omit needless words, and Usability testing. In Don't Make Me Think, the early concepts sharpen diagnosis, the middle concepts alter the response, and the later concepts make that response more sustainable, measurable, or appropriately constrained. Isolating one catchy phrase loses much of that architecture.
This sequence also explains why implementation should start small. A limited trial can reveal whether Steve Krug's proposed mechanism is present in the reader's situation, whether the cost of change is acceptable, and whether improvement lasts beyond initial enthusiasm. Positive evidence justifies expansion; weak evidence justifies revision. That is a stronger standard than simply feeling persuaded while reading.
The final test of Don't Make Me Think is whether it improves repeated decisions. Give a user a realistic task without instructions, watch silently, note every hesitation, simplify labels and hierarchy, remove unnecessary text, and repeat the test after changes. Used this way, Don't Make Me Think becomes a model that can be tested and adapted rather than a rigid formula.
Practical application
Practical application
Give a user a realistic task without instructions, watch silently, note every hesitation, simplify labels and hierarchy, remove unnecessary text, and repeat the test after changes.
A useful implementation rule is to start with one situation rather than attempting to redesign an entire life or organization at once. Write down the current behavior or decision process, identify which concept from Don't Make Me Think is most relevant, and define a small change that can be observed. Decide what evidence would count as improvement before starting.