All frameworks and cheat sheets

Checklist

Six rules for asking usability test questions

Checklist of six rules for usability test questions: never lead, do not ask users to design, watch behavior, ask why, stay quiet, trust what you observe.
A participant who says this is fine while clicking the wrong thing three times still has a usability problem.

Six rules for the way you ask questions in a usability test, so the questions do not bias what you see. Ask neutral questions, keep design opinions out of it, value behavior over stated preference, ask for the reasoning behind a struggle, say as little as possible during tasks, and count what you observe even when the participant reports no problem. Pin it next to your script before the first session.

Where this appears

What's in this checklist

  • Never lead: ask how was that, not was that easy
  • Do not ask users to design the interface
  • Separate what people do from what they say they prefer
  • Ask why, not do you like it
  • Stay quiet during tasks and let silence do the work
  • Trust problems you observe over problems people report

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/usability-test-question-rules-checklist"><img src="https://www.koji.so/visuals/usability-test-question-rules-checklist/usability-test-question-rules-checklist.png" alt="Checklist of six rules for usability test questions: never lead, do not ask users to design, watch behavior, ask why, stay quiet, trust what you observe." width="1200" height="630" /></a>
<p>Source: <a href="https://www.koji.so/visuals/usability-test-question-rules-checklist">Six rules for asking usability test questions</a>, Koji</p>