Summary
A usability test script must establish psychological safety ('we're testing the product, not you'), obtain consent, and position the moderator as a neutral guide. The think-aloud instruction is the cornerstone of moderated testing. Write human-centric scenarios, not system-centric tasks. Use the 'Boomerang' technique to turn user questions back into mental model insights.
A great usability test depends on what you say and when you say it. The wrong words create bias. The right words unlock honest feedback.
This guide provides copy-paste script elements you can use immediately.
The Intro: The First 5 Minutes
The start sets the tone for the entire session. Your script must cover three essential elements: the goal, the consent, and your role.
Element 1: The Goal
Participants often worry they are being evaluated. Eliminate this anxiety immediately.
Script:
"Before we start, I want to be clear about something important: we are testing the product, not you. There are no right or wrong answers. If something is confusing or difficult, that's the product's fault, not yours. You literally cannot make a mistake today."
Why it matters: Anxious participants behave differently. They ask permission, hesitate to criticize, and try to "succeed" rather than behave naturally. This statement gives them psychological safety.
Element 2: The Consent
You must obtain explicit consent for recording before you start.
Script:
"I am going to record this session—both the screen and our conversation—so I can share the highlights with my team. They weren't able to join today, and the recording helps me capture everything accurately. Is that okay with you?"
Wait for explicit verbal consent.
"Great. And just so you know, you can ask me to pause or stop the recording at any time."
Why it matters: Beyond legal requirements, asking for consent reinforces that the participant is in control. This builds trust.
Element 3: The Context (Neutral Guide)
Position yourself as a neutral observer, not the product's defender.
Script:
"One more thing: I didn't build this product, so you won't hurt my feelings with honest feedback. In fact, the more honest you are, the more helpful this is. If something frustrates you, tell me. If you hate something, say so. I'm here to learn, not to defend."
Why it matters: Participants naturally soften criticism when they think they are talking to the creator. Establishing neutrality unlocks candid feedback.
The Complete Intro (Copy-Paste)
"Thank you for joining me today. Before we dive in, I want to cover a few things.
First, we are testing the product, not you. There are no right or wrong answers.
If something is confusing or difficult, that's the product's fault, not yours.
You cannot make a mistake today.
Second, I am going to record this session—both the screen and our conversation—
so I can share the highlights with my team. Is that okay with you?
[Wait for consent]
Great. And you can ask me to pause or stop the recording at any time.
Finally, I didn't build this product, so you won't hurt my feelings with
honest feedback. The more honest you are, the more helpful this is.
Do you have any questions before we start?"
For how heuristic evaluation identifies what to focus testing on, see Heuristic Evaluation: The Audit Before the Test.
The Think-Aloud Instruction
The think-aloud protocol is the cornerstone of moderated usability testing. It externalizes the participant's internal thought process so you can understand what they are experiencing.
The Core Instruction
Deliver this before the first task:
Script:
"As you work through each task, please think out loud. Tell me what you are looking for, what you expect to happen when you click something, and if anything confuses you. I want to hear your internal monologue—what's going through your head as you navigate."
"It might feel a little weird at first, but it really helps me understand your experience. There's no need to explain or justify—just narrate what you're thinking."
The Nudge
Participants will go silent. When they do, gently prompt without leading:
| Situation | Prompt |
|---|---|
| Participant goes quiet | "What's going through your mind right now?" |
| Participant stares at screen | "What are you looking for?" |
| Participant hesitates | "What are you thinking about?" |
| Participant clicks without explaining | "What made you click there?" |
Common Mistakes
| Mistake | Problem | Fix |
|---|---|---|
| "Tell me what you're doing" | Describes actions, not thoughts | "Tell me what you're thinking" |
| Prompting constantly | Disrupts natural flow | Wait, then prompt gently |
| "Why did you do that?" | Sounds like criticism | "What made you choose that?" |
| Not demonstrating | Participant doesn't understand | Model think-aloud yourself briefly |
Modeling Think-Aloud
If a participant struggles with the concept, briefly demonstrate:
Script:
"Let me show you what I mean. If I were looking for where to change my password, I might say: 'Okay, I'm looking for something like Settings or Account... I see this gear icon, that usually means settings, so I'll click that... Now I'm scanning for something about security or password...'"
"Does that make sense? Just narrate what's in your head as you go."
For the moderation skills that bring these scripts to life, see The Art of Moderation.
Writing Scenarios, Not Tasks
The way you phrase tasks determines what you learn. System-centric instructions test whether users can follow directions. Human-centric scenarios test whether they can accomplish goals.
System-Centric (Bad)
"Go to Settings and change your password."
Problems:
- Tells them where to go (no findability test)
- Uses system language ("Settings")
- Tests instruction-following, not navigation
Human-Centric (Good)
"Imagine you suspect someone may have accessed your account without permission. Show me how you would secure it."
Benefits:
- Does not reveal the path
- Uses human language ("secure it")
- Tests the full mental model
- Mirrors real-world motivation
The Transformation Formula
| System-Centric | Human-Centric |
|---|---|
| "Click the cart icon and check out" | "You're ready to buy these items. Complete your purchase." |
| "Use the filter to show only blue products" | "You only want to see blue options. Show me what you'd do." |
| "Go to Help and find the refund policy" | "You want to return something. Find out if that's possible." |
| "Add a new team member in the admin panel" | "Your colleague Alex just joined the team. Get them access." |
Scenario Components
A complete scenario includes:
| Component | Purpose | Example |
|---|---|---|
| Context | Why they are doing this | "You're planning a trip next month..." |
| Goal | What they want to achieve | "...and you want to find flights under €200." |
| Trigger | What prompts action | "Show me how you'd do that." |
Complete Example:
"Imagine you just received an email saying your subscription is about to renew, but you want to cancel before you're charged. Starting from this homepage, show me how you would handle that."
Neutral Probing: The Boomerang Technique
During a session, participants will ask you questions. Your instinct is to help. Resist it.
Every question they ask reveals something about their mental model. If you answer, you lose that insight and bias their behavior.
The Problem
Participant: "Does this button save my changes?"
You (wrong): "Yes, that saves everything."
You have just:
- Confirmed their hypothesis without testing it
- Lost the opportunity to understand their uncertainty
- Potentially changed their behavior going forward
The Boomerang
Turn questions back to reveal mental models:
| User Question | Boomerang Response |
|---|---|
| "Does this button save?" | "What would you expect it to do?" |
| "Is this the right place?" | "What makes you think it might be?" |
| "Did that work?" | "What would tell you if it did?" |
| "What does this icon mean?" | "What do you think it might mean?" |
| "Should I click here?" | "What do you think would happen if you did?" |
| "Is this what you wanted me to do?" | "What makes you ask that?" |
The Follow-Up
After they answer, you can proceed:
Participant: "What does this icon mean?"
You: "What do you think it might mean?"
Participant: "Maybe... settings? Or preferences?"
You: "Okay, let's try it and see what happens."
Now you have learned:
- They were uncertain about the icon
- They guessed "settings or preferences"
- You can observe whether their mental model was correct
When to Break the Rule
There are rare exceptions when you should answer directly:
| Situation | Response |
|---|---|
| Safety concern | "Let me stop you there—that would actually delete your data." |
| Complete dead end | After exhausting exploration: "In this case, you'd go to Account Settings." |
| Technical failure | "That's a bug in our prototype, not something you did. Let me reset it." |
| Participant frustration | If they are genuinely upset, prioritize their wellbeing. |
The Complete Session Flow
For how test scripts operationalize the research plan, see The Research Plan.
What This Means for Practice
A good script is invisible. It creates the conditions for honest, natural behavior without the participant noticing they are being guided.
- Set the tone in the intro: "Testing the product, not you" unlocks honesty
- Teach think-aloud explicitly: Do not assume participants know how
- Write scenarios, not tasks: Test findability, not instruction-following
- Boomerang every question: Their questions are data; your answers are bias
- Practice the script: Fluency makes it feel natural, not scripted
The goal is to observe authentic behavior. Every word you say either supports or undermines that goal.