Handbook of Usability Testing: How to Plan Tests That Produce Real Insights

Usability testing looks easy: put a user in front of the product and watch. The Handbook of Usability Testing by Jeffrey Rubin and Dana Chisnell has been the field’s standard guide for decades precisely because it is not easy. Most tests fail in the planning, and the failures are invisible until you act on wrong findings.

What does the handbook teach about objectives?

Start with the decision, not the product. A test without objectives produces anecdotes; a test with them produces answers. Write down what you need to learn and what you will do with each possible finding. If a finding would not change anything, stop testing for it.

Why does recruiting decide everything?

Because testing the wrong users teaches you about the wrong users. The handbook is strict on this: participants must match your real users’ goals, experience, and context. Testing your fintech app on colleagues, or on anyone who will say yes, generates findings that feel like insight and behave like noise. Recruiting is where test quality is won, and it is the part teams most often shortcut.

How should tasks be written?

As goals, not instructions. “Find and book the cheapest flight to Cairo next Friday” reveals how users think. “Click the flights tab, then enter Cairo” tests whether users can follow directions, which tells you nothing about your navigation. Realistic tasks include the messiness of real goals; scripted click-throughs sanitize the confusion you were testing to find.

What is the pilot test for?

Everything fails in rehearsal: confusing tasks, broken prototypes, timing problems. The pilot is where these fail cheaply.

Why does Tremoloo share this book?

Because its planning discipline matches our own research practice, and clients who understand it get far more from every test we run.

Want usability tests planned to this standard? Book our usability testing team.