How to Write a Usability Testing Script (With Real Examples)
A great usability testing script is the difference between rich insights and wasted sessions. Learn the anatomy of an effective script with real example tasks, questions, and facilitation prompts.
Why the Script Matters
Your test script is your session protocol — the backbone of consistent, comparable data across participants. A poorly written script produces inconsistent results, biased responses, and gaps in your data. A well-crafted script keeps you on track, prevents leading questions, and ensures every participant receives the same baseline experience.
The Five-Part Script Structure
1. Introduction (5 min)
Set expectations, build rapport, and remove performance anxiety.
Example: "Thanks for being here today. We're testing a design — not testing you. There are no right or wrong answers. If you find something confusing, that's incredibly useful feedback. Please think out loud as you work."
2. Background Questions (5 min)
Warm-up questions to understand the participant's context.
Example: "How often do you shop online?" / "When was the last time you used a [product type]?" / "What tools do you typically use for [task]?"
3. Tasks (20–30 min)
Scenario-based, action-oriented instructions with no navigation hints.
Bad: "Find the settings page and change your password."
Good: "Imagine you've been using this app for a month. You're worried about your account security and want to update your password. Starting from the home screen, go ahead."
After each task, ask: "On a scale of 1–7, how easy or difficult was that? Why?"
4. Post-Task Debrief (5–10 min)
Capture overall impressions.
Example questions: "What stood out most to you?" / "Was there anything that surprised you?" / "If you could change one thing, what would it be?"
5. Wrap-Up (2 min)
Thank the participant, confirm incentive delivery, and ask if they have questions for you.
Common Script Mistakes
- Leading tasks: "Click the checkout button" tells users where to go before they've decided.
- Jargon: Use the participant's language, not your internal product terminology.
- Too many tasks: 3–5 tasks per 60-minute session. More and you rush; less and you leave questions unanswered.
- Forgetting the think-aloud reminder: Participants drift silent. Re-prompt: "What are you thinking right now?"
Key Takeaways
- Script = protocol. Consistency across participants makes your data comparable.
- Scenario-based tasks over instruction-based tasks — observe decisions, not execution.
- 3–5 tasks per session is the right density for a 60-minute moderated test.
- Post-task ratings (Likert scale) give you quick quantitative data alongside qualitative observation.
A well-structured usability script has five parts — each serving a distinct purpose from building rapport to gathering closing impressions.
