Usability test survey
Usability data is most reliable right after the task, while the experience is still raw. This template captures whether people finished, where they got stuck, and a single-ease rating you can compare across tasks and rounds.
Best for: Researchers and PMs running moderated or unmoderated usability tests.
Use this template free1 of 7
Which task did you just attempt?
A live preview of this template. Click through it. Nothing gets sent.
The questions
- 1Which task did you just attempt?Short textPin each response to a specific task so you can compare across them.
- 2Were you able to complete it?Single selectCompleted / Completed with difficulty / Did not complete — the core success measure.
- 3Overall, how easy or difficult was that task?Opinion scaleThe Single Ease Question (SEQ): 1 very difficult to 7 very easy. One number you can trend.
- 4Where exactly did you get stuck or hesitate?Long textAsk while the moment is fresh — recall of friction fades within minutes.
- 5Was there anything confusing about the labels or wording?Long text
- 6What did you expect to happen that didn't?Long textMismatched expectations point straight at the broken mental model.
- 7How confident were you that you did it correctly?Opinion scale1-7 — low confidence on a 'completed' task flags a hidden usability problem.
How to run it well
- Fire the SEQ immediately after each task, not at the end of the session — a single end-of-test rating blends every task into one useless average.
- Watch for tasks marked 'completed' with low confidence; that gap is where people muddle through without understanding, and it predicts future support tickets.
- Tag stuck points by screen and element so the same wording or button shows up as a pattern, not a one-off.
- Keep the task wording neutral in the prompt — telling people what to click teaches them the answer and hides the real friction.
FAQ
Why use the SEQ instead of a longer usability questionnaire?
The Single Ease Question is one 7-point item that correlates well with longer instruments and gets answered every time. For per-task feedback, completion plus SEQ plus a stuck-point verbatim is enough to act on.
How many participants do I need per task?
Five users typically surface the majority of severe usability problems on a given task. For comparing SEQ scores between designs you'll want more — closer to 15-20 per variant for a stable mean.
Can I run a usability test asynchronously as a form?
Yes. Pair the prototype or live build with this form so people self-report right after each task. You lose the live observation, but you gain reach and remove moderator bias from the answers.
Related templates
- Team pulse surveyWorkload, clarity, blockers, one change — short, recurring, anonymous.
- Feature request surveyCapture the job behind each request, the workaround, and how often it bites.
- Brand perception surveyFirst word, what you're known for, and who they'd recommend you to.
- Customer interview screenerScreen interviewees by real behavior, not by who's eager to talk.