Usability Testing Script Template: Free Guide + Example

A solid script keeps usability sessions consistent and reduces moderator bias. Use this template to run clear, repeatable sessions.

What you'll get:

A usability testing script template
Task and probing question examples
A simple analysis checklist

Use the sections below as building blocks; keep what you need and delete the rest.

Need the full study doc? Use the usability testing template.

References for this guide are listed at the end.

What is a usability testing script?

Lyssna defines a usability test script as an outline that guides what a moderator says, including introductions, prompts, and follow-up questions. GitLab adds that the script keeps sessions consistent and aligned to research objectives.

Why use a script?

Maze notes that a script keeps methodology consistent, helps timing, and provides a roadmap for what to say. GitLab highlights that scripts keep sessions consistent and easier to analyze.

Core sections of a script

Maze and GitLab both structure scripts into four parts:

Introduction and consent
Warm-up questions
Tasks and observations
Wrap-up questions

Usability testing script template (copy/paste)

1. Introduction and consent

Columbia University provides a sample facilitation script that emphasizes consent, recording, and that the test is about the product, not the participant.

Hello, thanks for joining today. My name is [Name], and I work on [Team].
We are testing the product, not you. There are no wrong answers.
The session will take about [Time] minutes.
We would like to record this session for research purposes. Do we have your consent?
If you need a break at any time, let me know.
Please think aloud as you work. This helps us understand your experience.

2. Warm-up questions

GitLab suggests short warm-up questions to set context and build rapport.

What is your role and what are your main responsibilities?
How often do you do [task or workflow]?
What tools do you use today?

3. Task instructions

Lyssna recommends 3 to 5 tasks with clear scenarios. GitLab recommends task wording that avoids UI labels and reflects real user goals.

Task 1 (scenario): You want to [goal]. Please show me how you would do that.

Task 2 (scenario): You need to [goal]. Use the product as you normally would.

Task 3 (scenario): You are trying to [goal]. Please think aloud as you go.

4. Probing questions during tasks

Maze recommends asking open-ended questions about steps, expectations, and decisions.

What are you thinking right now?
What did you expect to happen?
Why did you choose that option?
What would you do next?

5. Wrap-up questions

Maze and GitLab recommend a short wrap-up to capture overall impressions.

What worked well?
What was confusing or frustrating?
If you could change one thing, what would it be?

Note-taking worksheet

User Interviews highlights the need for structured notes during usability tests to keep sessions consistent and easier to analyze.

Field	Notes
Participant
Task
Success or failure
Time on task
Observations
Quotes
Issues and severity

Analysis checklist

[ ] Review notes per task and participant
[ ] Identify common failure points
[ ] Capture quotes that explain why
[ ] Summarize top issues and opportunities

Mini example (filled in)

Goal: Test if users can find pricing details
Tasks: Find pricing page, compare plans, start a trial
Insight: Users looked for pricing in the top nav and missed it in the footer

FAQ

How long should a usability test session be?

Maze recommends keeping sessions around 30 minutes, and GitLab notes that 30 to 45 minutes is a typical range.

How many tasks should I include?

Lyssna suggests 3 to 5 tasks. Maze recommends keeping task count under eight.

What should a script include?

Maze and GitLab both outline four parts: introduction, warm-up questions, tasks, and wrap-up.

References

Related resources

If you want a fast UX review for a specific page, start here: Website UX Audit

Want client-ready UX findings in minutes? Roast My Web generates branded PDF audit reports with prioritized UX, conversion, and SEO fixes.