Usability test survey
Ask about a task right after people try it, while it's still fresh. This template records whether they finished, where they got stuck, and one ease rating you can compare across tasks and test rounds.
Best for: Researchers and product teams running moderated or unmoderated usability tests.
Use this template freeWhich 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 textPins each answer to one task so you can compare tasks.
- 2Were you able to complete it?Single selectCompleted / Completed with difficulty / Did not complete. This is your main success measure.
- 3Overall, how easy or difficult was that task?Opinion scaleThe Single Ease Question (SEQ), 1-7, from very difficult to very easy. One number you can track.
- 4Where exactly did you get stuck or hesitate?Long textAsk while the moment is fresh. People forget small hesitations quickly.
- 5Was there anything confusing about the labels or wording?Long text
- 6What did you expect to happen that didn't?Long textA gap between what people expected and what happened shows you how they think the product works.
- 7How confident were you that you did it correctly?Opinion scale1-7. Low confidence on a finished task points to a problem nobody reports.
Sample replies, counted
These replies are made up to show the method.
Asked: Where exactly did you get stuck or hesitate?
Couldn't find where to invite someone. I checked Settings first, then the profile menu.
Invite button hiddenWasn't sure if 'Member' or 'Editor' could change billing.
Role names unclearthe invite link is under the share icon?? took me a while
Invite button hiddenI typed the email and pressed enter and nothing happened, had to click Add.
Email field confusingLooked for a + next to the team list. There isn't one.
Invite button hiddenEditor vs Admin, no idea what the difference is.
Role names unclearIt said 'pending' and I didn't know if the email had gone out.
Email field confusing
| Label | Replies |
|---|---|
| Invite button hidden | 3 |
| Role names unclear | 2 |
| Email field confusing | 2 |
Three of seven people looked for the invite in the wrong place, and each looked somewhere different. Move or repeat the invite entry where they looked first, then explain the roles in one line next to the picker.
How to run it well
- Ask the SEQ straight after each task, not once at the end. One rating at the end blends every task into a single average that tells you nothing.
- Look for tasks marked 'completed' with low confidence. People got through without understanding, and those are tomorrow's support tickets.
- Tag each stuck point by screen and element. Then the same button or label shows up as a pattern instead of a one-off.
- Keep the task wording neutral. If the prompt says what to click, you've given away the answer and hidden the friction.
When not to use this: Skip this if you haven't built or prototyped anything yet. You can't test a task that doesn't exist, so start with a user interview script about how people do it today.
FAQ
Why use the SEQ instead of a longer usability questionnaire?
How many people do I need per task?
Can I run a usability test asynchronously as a form?
Where the method comes from
Related templates
- Team pulse surveyWorkload, clarity, blockers, one change. Short, recurring, anonymous.
- Feature request surveyThe job behind each request, the workaround, and how often it comes up.
- Brand perception surveyFirst word, what you're known for, and who they'd recommend you to.
- Customer interview screenerScreen interviewees by what they've done, not by who's keen to talk.