korrents

korrents · books

Don't Make Me Think, Revisited (New Riders, 2014, third edition)

Steve Krug · c. 2000–2014

Read the book on books.google.com ↗

5 people recommend it, on rcmnd ↗

15 korrents from this book ↓

Steve Krug did not write this page.

Every claim below was made in this book, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The book prints chapter headings its extracted text does not preserve, so the claims below are in the book's order but not grouped. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. I should be able to “get it” —what it is and how to use it - without expending any effort thinking about it.

    See it on the page ↗

  2. We don't read pages. We scan them. One of the very few well-documented facts about Web use is that people tend to spend very little time reading most Web pages.

    See it on the page ↗

  3. We don't make optimal choices. We satisfice.

    See it on the page ↗

  4. The answer is that it matters a great deal because while muddling through may work sometimes, it tends to be inefficient and error-prone.

    See it on the page ↗

  5. If you can make something significantly clearer by making it slightly inconsistent, choose in favor of clarity.

    See it on the page ↗

  6. It doesn't matter how many times I have to click, as long as each click is a mindless, unambiguous choice.

    See it on the page ↗

  7. Get rid of half the words on each page, then get rid of half of what's left.

    See it on the page ↗

  8. The main thing you need to know about instructions is that no one is going to read them — at least not until after repeated attempts at “muddling through” have failed.

    See it on the page ↗

  9. And, like most religious debates, they rarely result in anyone involved changing his or her point of view.

    See it on the page ↗

  10. The only problem is, there is no Average User.

    See it on the page ↗

  11. Testing always works, and even the worst test with the wrong user will show you important things you can do to improve your site.

    See it on the page ↗

  12. Testing one user early in the project is better than testing 50 near the end.

    See it on the page ↗

  13. I think every Web development team should spend one morning a month doing usability testing.

    See it on the page ↗

  14. And by definition, affordances are the last thing you should hide.

    See it on the page ↗

  15. The reservoir is limited, and if you treat users badly enough and exhaust it there's a good chance that they'll leave.

    See it on the page ↗

Related books

Found from what the books talk about: claims worded alike in the archive's hourly pass, and subjects both are filed under. It is not a judgement that they agree — related books often argue the opposite. All books

Keep reading

The other pieces are the ones whose claims are worded most like this one's. That measures language, not agreement: they may argue the opposite.