What I’m Reading: Don’t Make Me Think

What I’m Reading: Don’t Make Me Think

Don’t Make Me Think- Revisited a Common Sense Approach to Web and Mobile Usability, by Steve Krug

Don't Make Me Think Cover Image

My thoughts:

Don’t make me Think is a book about building, assessing, and testing for usability. I found this to be a fascinating read.  Krug has a conversational writing style, and the book is full of visual examples.  The content of this book reinforced my instincts to design with the user in mind. Krug is straight forward and sticks to his claim that most of the ideas he outlines are “common sense” and indeed, I did find that his theories reinforced my instincts as a designer and named many of my frustrations as a user. The concept of “not making your users think” is simple, it should not be hard for users to use sites.

What I’m taking away:

This book is packed with useful information and outstanding guidelines that I want keep in mind as a move forward as a developer/designer.

Whatever you are designing should be as many of these things as possible:

In the first chapter Krug introduces this list of guidelines to help keep you on track when reviewing or building. I’m working on memorizing this list, but until then I will keep it handy as a checklist.

  • Useful
  • Learnable
  • Memorable
  • Effective
  • Efficient
  • Desirable
  • Delightful

Language matters

Using common naming conventions and simple titles is important.  Naming buttons is not the time to get clever.  Call things what they are.

Sites are not read, they are scanned

Users scan pages and look for the first reasonable option.

Stick to the following to support scanning:

  • Conventions (use standards that are common and recognizable)
  • Visual hierarchies (use headings to highlight importance)
  • Clearly defined areas (use blank space and boarders to keep things visually organized)
  • Distractions (limit these as much as possible)
  • What’s clickable (should be obvious with standard visual cues)
  • Support scanning (use short paragraphs, lists, and highlight key terms)

Clicks matter

To a degree clicks matter, but what matters more is how hard those clicks were to achieve. Did your users have to spend mental capital to figure out what to click?

Writing for the web

Try to eliminate “Happy talk,” and keep instructions to a minimum. Keep paragraphs short and eliminate all extra words.  Effective writing for the web is about being concise.


Every site should have the following:

  • A sense of Scale (how big and deep does this go?)
  • Direction (where am I heading, how do I get there?)
  • Location (where am I?)
  • Home (How do I start over?)
  • Search (Where is the thing I’m looking for?)

Krug recommends trying what he refers to as the “Trunk Test,” which basically means that users should at a glance be able to quickly and easily find the following:

  • Site ID
  • Page name
  • Sections
  • Local navigation
  • You are here indicators
  • Search

What goes on the Home page?

The Home page is a place to spell out the big picture.  A unique and informative tagline, a welcome blurb, and a way to learn more. Remember space is your friend, and you don’t need to promote every feature on the home page, but rather draw visitors in.

Arguments about usability are a waste of time-
Here I will directly quote Krug: “It’s not productive to ask questions like “Do most people like pull-down menus?” The right kind of question to ask is “does this pull-down, with these items, and this wording in this context on this page create a good experience for most people who are likely to use this site?”

User Testing

There is a difference between a focus group, and a user testing group.  A focus group can help you determine if a product should be developed, and user testing group will help you determine if you are designing it right. Krug recommends testing early and often and includes and entire section that covers user testing frequency, number of users, who to test, how to find test users, where to do the testing, who observes, what to test, and a step by step guide for testing, including a script and possible problems, and deciding what to fix.

Reservoir of Goodwill

Krug introduces a user’s patience with a site as the “reservoir of goodwill: it’s size varies from person to person, its situational, and refillable, and a single mistake can empty it. Hidden information, forced conventions (dashes between phone numbers), asking for unneeded information, and looking amateurish all deplete the reservoir. While making choices obvious and ease, information informative, saving steps, and anticipating and answering user questions work toward filling the reservoir.


Accessibility benefits everyone and it is the right thing to do. Although it can seem like more work, and sometimes can compromise design, designing with your users in mind means adopting as many accessibility standards as possible.

Who should read this book?

I found this book incredibly informative and can recommend it whole heartedly.  Web developers should read this book, application designers, CEO’s and Project Managers should read this book.  Web users should read this book and start demanding better from the products we use.  Our lives are better lived with better experiences, and that starts with designing for the user.

Leave a Reply

Your email address will not be published. Required fields are marked *