Usability testing script template: a ready-to-use guide
Stop rewriting from scratch. This usability testing script template covers every phase of a session, with real example prompts you can copy today.
Usability testing script template: a ready-to-use guide
A usability testing script is a written guide that keeps your session consistent, your prompts neutral, and your observations comparable across participants. Without one, moderators inadvertently lead participants, skip important tasks, or forget to capture debrief data. The template below covers every phase of a standard moderated session and can be adapted for remote or in-person contexts.
Why a script matters more than you think
Moderator influence is one of the most common threats to usability data quality. When you improvise prompts, you risk phrasing a task in a way that points participants toward the answer. A script forces you to write neutral prompts in advance and review them with a colleague before the session.
Scripts also create a shared research artifact. When multiple team members moderate sessions, a standardized script means every participant heard the same instructions. That consistency is what makes it valid to compare Task A completion rates across ten different participants.
For teams running moderated usability testing, a script is non-negotiable. Even for unmoderated sessions, written task prompts and instructions serve the same function.
The anatomy of a usability testing script
A complete script has five sections:
- Introduction and consent
- Warm-up questions
- Task prompts (one block per task)
- Post-task questions
- Debrief and closing
Template: section by section
1. Introduction and consent
Read this section verbatim.
“Thank you for joining us today. My name is [Name] and I am a researcher at [Company]. I have a colleague on the call as an observer, and with your permission we will be recording today’s session.
Before we start, I want to make a few things clear. We are testing the product, not you. There are no right or wrong answers. If something is confusing, that is valuable feedback for our team.
You can stop at any time. If you would prefer not to answer a question or complete a task, just let me know.
Do you have any questions before we begin? [Pause.]
Are you comfortable with us recording today’s session for internal research purposes only? [Wait for verbal confirmation or collect written consent before proceeding.]“
2. Warm-up questions
Warm-up questions build rapport and give you baseline context about the participant. Keep this under five minutes.
- “To start, can you tell me a little about what you do day to day?”
- “How often do you use [product category] tools in your work?”
- “When was the last time you [performed the core behavior your product supports]?”
Moderator note: Listen for vocabulary the participant uses. Mirror their language in follow-up probes rather than introducing product terminology.
3. Task prompts
Write one block per task. Each block includes the scenario, the prompt, and success criteria. Success criteria are for your internal scoring after the session, not something you share with the participant.
Task 1
Scenario: “Imagine you have just joined a new team and your manager has asked you to [realistic scenario relevant to your product, e.g., ‘set up a new project and invite two teammates’].”
Prompt (read aloud): “Please go ahead and do that now. Remember to think aloud as you work.”
Success criteria (internal):
- Completes task without assistance: Yes / No
- Number of errors observed: ___
- Time on task (start: ___ / end: ___): ___
- Observed pain points: ___
Task 2
Scenario: “Now imagine you want to [second core workflow, e.g., ‘find the report you created last week and download it as a PDF’].”
Prompt (read aloud): “Please go ahead. Feel free to talk through what you are doing.”
Success criteria (internal):
- Completes task without assistance: Yes / No
- Number of errors observed: ___
- Time on task: ___
- Observed pain points: ___
Repeat this block for each additional task. Nielsen Norman Group recommends five participants to uncover the majority of usability problems, but your task list should be scoped to fit comfortably within your session time.
Think-aloud prompts to use mid-task (as needed):
- “What are you thinking right now?”
- “What did you expect to happen there?”
- “What would you do next if you were on your own?”
- “How does that compare to what you expected?“
4. Post-task questions
Ask these after each task or after a group of related tasks.
- “On a scale of one to seven, how easy or difficult did you find that task? One is very difficult, seven is very easy.”
- “What was the most confusing part of that process?”
- “Was there anything that worked the way you expected?”
- “If you could change one thing about that flow, what would it be?”
Moderator note: If the participant struggled, resist the urge to explain how the feature works. Your job is to observe and record, not to teach.
5. Debrief and closing
This section is more conversational. Cover all questions but feel free to follow the participant’s lead.
- “Now that you have had a chance to try out [product name], what is your overall impression?”
- “Which part felt the most intuitive?”
- “Which part would you most want the team to improve?”
- “Is there anything you expected to be able to do that you could not find?”
- “Do you have any questions for me before we wrap up?”
Closing:
“Thank you so much for your time. Your feedback is genuinely helpful. We will share your [incentive details] within [timeframe]. Have a great rest of your day.”
Key fields to track in your session log
Keep a running log alongside the script so you can compare sessions quickly:
| Field | Task 1 | Task 2 | Task 3 |
|---|---|---|---|
| Task completed (Y/N) | |||
| Time on task | |||
| Number of errors | |||
| Think-aloud highlights | |||
| Post-task ease rating (1-7) | |||
| Notable quotes |
Adapting the template for different contexts
Remote moderated sessions
Add a short technical check at the top of your introduction: “Before we start, can you confirm you can see your screen share? Great. If at any point the connection drops, I will call you back at the number you provided.”
For remote sessions, also confirm screen recording consent in writing before the session using a tool like Calendly or a dedicated consent form.
Unmoderated sessions
Remove the moderator-spoken sections. Replace them with written instructions the participant reads independently. Add a video introduction (under two minutes) that explains the think-aloud protocol because participants cannot ask for clarification mid-session.
Unmoderated usability testing tools like Maze or UserTesting handle script delivery for you, but you still need to write clear task prompts. The same neutral-language rules apply.
Mobile app testing
Add a device-sharing section: “I am going to ask you to share your screen from your phone. Here is how to do that on iOS / Android: [steps].” Mobile sessions also benefit from a task log that notes which gestures the participant attempted, not just whether they completed the task.
Common script mistakes to avoid
Giving away the answer in the scenario. A prompt like “Use the search bar to find your last order” tells the participant exactly which UI element to use. Instead: “Find the order you placed last week.”
Stacking multiple actions in one prompt. “Log in, find your settings, update your email address, and save” is four tasks. Break them apart so you can identify where friction occurs.
Forgetting to collect timestamps. Time on task is one of the most objective usability metrics. Note start and end times for every task, or use a tool that captures them automatically.
Skipping the warm-up. Participants who jump straight into tasks are often nervous, which affects their behavior. Three minutes of easy conversation dramatically improves data quality.
Running sessions at scale
If you are running more than five or six sessions, consistency across moderators becomes critical. Pair your script with a shared session log template and a pre-session briefing so every moderator knows the success criteria and approved follow-up probes.
Platforms like CleverX combine verified participant recruitment with AI-moderated sessions, which means the AI follows your script precisely across every session without drift. That consistency is especially valuable when you are running usability testing for B2B products with hard-to-recruit professional audiences, where each session slot is expensive and needs to count.
For teams building out their broader research process, the how to create a usability testing plan guide covers the full planning workflow, while how to do usability testing effectively walks through execution in detail.
Frequently asked questions
What is a usability testing script?
A usability testing script is a written guide a moderator follows during a session. It includes an introduction, consent language, task prompts, and closing questions. Having a consistent script reduces moderator bias and makes it easier to compare findings across participants.
How long should a usability testing script be?
Most scripts for a 60-minute session run two to four pages. The introduction and consent section takes five to ten minutes, tasks take thirty to forty minutes, and the debrief takes ten to fifteen minutes. Keep task prompts short, typically one to two sentences each.
Should I read the script word for word?
You should read the introduction and consent section verbatim to stay legally consistent. Task prompts can be read verbatim or paraphrased slightly, but avoid wording that hints at the correct path. The debrief can be more conversational as long as you cover your core questions.
How many tasks should a usability test script include?
Aim for three to six tasks in a 60-minute session. More than six tasks often leads to participant fatigue and rushed observations. Prioritize the workflows that carry the highest risk or represent the most common user journeys in your product.
What is the ‘think-aloud’ protocol and how do I prompt it?
Think-aloud is a technique where participants narrate their thoughts as they interact with the product. After explaining it in the introduction, prompt participants during tasks by saying things like ‘What are you thinking right now?’ or ‘Tell me what you expected to happen there.’ It is the single most useful data-collection technique in moderated usability testing.
Can I use the same script for moderated and unmoderated testing?
Partly. Task prompts and success criteria can be reused. However, the introduction, consent, and debrief must be adapted for unmoderated sessions because there is no live moderator to answer questions or prompt think-aloud. Unmoderated scripts also need clearer standalone instructions since participants cannot ask for clarification.