Moderated usability test script
A full moderator script — from the welcome and think-aloud instructions through tasks, probes, and debrief — so every session runs consistently and without bias.
Researchers and designers moderating usability sessions — they spend their days facilitating sessions and fighting their own instinct to help, explain, or lead — the habits that quietly ruin usability data.
- What they're trying to learn
- run consistent, unbiased moderated sessions that produce comparable, trustworthy findings.
- Who they interview
- recruited participants matching the study criteria
Use this as the backbone script for any moderated session — in person or remote. Keep the wording consistent across participants so findings are comparable.
Moderated script questions to copy & run
Intro & consent
- 1.Thanks for joining. Today I'll ask you to try a few tasks with [product] and think out loud as you go.
- 2.There are no right or wrong answers — we're testing the product, not you. If something's confusing, that's useful information.
- 3.Is it okay if I record this session for our notes? It stays internal.
- 4.Do you have any questions before we begin?
Warm-up
- 1.To start — tell me a bit about your role and how you use tools like this.
- 2.When was the last time you did [the relevant task]? Walk me through it.
Tasks & probes
- 1.Here's your first task: [realistic task]. Take your time and think out loud.
- 2.(Probe) What are you thinking right now?
- 3.(Probe) What did you expect to happen there?
- 4.(If stuck) What would you try if I weren't here?
- 5.(After each task) How was that on a scale of very easy to very hard? Why?
Debrief & close
- 1.Overall, what stood out — good or bad?
- 2.If you could change one thing, what would it be?
- 3.Is there anything I should have asked but didn't?
- 4.Thank you — that was really helpful.
Tips for better answers.
- Read the intro consistently every time so sessions are comparable.
- Stay neutral and quiet during tasks; the hardest moderator skill is not helping.
- Use scripted probes ('What did you expect?') instead of improvised leading questions.
- Separate observation from interpretation in your notes; save the 'why' for synthesis.
Questions about this template.
What should a moderated usability test script include?
A consistent intro and consent, a short warm-up, realistic tasks with neutral probes, a post-task difficulty check, and a debrief. Scripting these keeps sessions comparable and reduces the moderator bias that skews findings.
How do I avoid leading participants as a moderator?
Use pre-written neutral probes, resist helping unless they're truly stuck, embrace silence, and remind participants you're testing the product, not them. Consistency in wording across sessions is your best defense against bias.
How long should a moderated session be?
Usually 30–60 minutes, depending on the number and complexity of tasks. Leave buffer for warm-up and debrief, and don't cram in so many tasks that participants fatigue and answers degrade.
Don't just ask the questions — synthesize the answers.
Save these questions as a template in Intervool, capture the interview, and let AI turn every conversation into insights, personas, and a prioritized roadmap. Free for 30 days.