Usability Test Script & Moderator Guide
Create detailed test scripts and moderator guides for running usability test sessions with specific tasks, questions, and facilitation tips.
Prompt
Create a usability test script and moderator guide for testing [feature/product]. Include:
1. Test Session Overview
- Test duration (typically 45-60 min)
- Session structure and timing
- Materials needed
- Recording and consent
- Participant compensation
2. Introduction Script (5 min)
**Welcome and Rapport Building:**
"Hi [Name], thanks for joining today. I'm [Your Name], and I'll be guiding you through this session. Before we start, I want to make sure you're comfortable. Do you have any questions before we begin?"
**Set Expectations:**
- Explain purpose of the test
- "We're testing the product, not you"
- There are no right or wrong answers
- We want honest feedback
- Think aloud protocol explanation
- OK to take breaks anytime
**Recording Consent:**
"For research purposes, we'll be recording this session. The recording is only for our team and won't be shared publicly. Are you comfortable with that?"
**Sign Consent Form:**
(If applicable)
3. Background Questions (5-7 min)
Get context about the participant:
- Current role and responsibilities
- Relevant experience with [product category]
- Current tools they use for [task]
- Frequency of use
- Pain points with current solution
- Technical comfort level
Example questions:
- "Tell me about how you currently [do task]?"
- "What tools do you use for this?"
- "What works well? What's frustrating?"
- "How often do you [do task]?"
4. Task Scenarios (25-30 min)
**Task Format:**
For each task, include:
- Task number and name
- Scenario setup (give context and motivation)
- Success criteria (what defines completion?)
- Time estimate
- Follow-up questions
**Think Aloud Prompts:**
Use these if participant goes quiet:
- "What are you thinking?"
- "What are you looking for?"
- "What do you expect to happen?"
- "What's going through your mind?"
**Example Tasks:**
**Task 1: [Task Name]**
Scenario: "Imagine you want to [motivation]. Show me how you would [action]."
Success: Participant completes [specific action]
Time: 5-7 minutes
Observe:
- Did they find the feature easily?
- Any hesitations or confusion?
- Path taken vs. expected path
- Errors or mistakes
- Time to completion
- Satisfaction level
Follow-up questions:
- "Was that what you expected?"
- "On a scale of 1-5, how easy was that?"
- "What would have made that easier?"
- "Did you notice [specific element]?"
[Repeat for Task 2, 3, 4, etc.]
5. Probing Questions
Use throughout the session:
- "Tell me more about that"
- "Why did you click there?"
- "What did you expect to see?"
- "How does this compare to [current tool]?"
- "What's confusing about this?"
- "What would you change?"
6. Post-Task Questions (5-7 min)
After all tasks:
- Overall impressions
- What worked well?
- What was frustrating?
- What's missing?
- Would you use this? Why or why not?
- How does this compare to [competitor]?
- Any final thoughts or suggestions?
**Rating Questions:**
- "On a scale of 1-5, how easy was it to [complete task]?"
- "How likely are you to recommend this to a colleague?" (NPS)
- "How satisfied are you with this experience?"
7. Closing (2-3 min)
- Thank the participant
- Ask if they have any questions
- Explain next steps
- Remind about compensation/incentive
- Provide contact info for follow-up
8. Moderator Tips
**Do:**
- Be neutral and encouraging
- Listen more than you talk
- Let silence happen (people need time to think)
- Take notes on observations
- Probe when you see confusion
- Thank them for feedback
- Keep track of time
**Don't:**
- Lead the participant
- Defend the design
- Explain how things work (unless they're completely stuck)
- Jump in too quickly to help
- Show disappointment at criticism
- Use jargon or technical terms
- Rush through tasks
9. Handling Challenges
**If participant is stuck (>2 min):**
- "What are you expecting to see?"
- "Where would you look for that?"
- If still stuck: Provide minimal hint
- Mark as task failure if can't complete
**If participant is quiet:**
- "What are you thinking right now?"
- "Can you walk me through what you're doing?"
**If participant asks you questions:**
- "What do you think would happen?"
- "What would you do in real life?"
- Redirect to their instincts
10. Note-Taking Template
For each task, track:
- [✓] Completed / [✗] Failed / [~] Completed with help
- Time to complete
- Path taken
- Errors or confusion points
- Direct quotes
- Severity: Critical / High / Medium / Low
- Emotions observed
- Suggestions made
11. Technical Setup Checklist
Before session:
- [ ] Recording software tested
- [ ] Screen sharing works
- [ ] Prototype/product accessible
- [ ] Note-taking template ready
- [ ] Consent form ready
- [ ] Backup plan if tech fails
- [ ] Quiet environment
- [ ] Phone on silent
Format as a complete, ready-to-use test script that a moderator can follow step-by-step during a usability test session.How to use
- 1Replace [feature/product] with what you're testing. Example: "our new checkout flow" or "dashboard redesign"
- 2Define your test goals: Before running prompt, identify what you want to learn
- 3Add context: Describe the product and test focus. Example: "Testing: Mobile app onboarding. Goal: Understand if first-time users can create account and complete profile."
- 4List specific tasks: Mention "Tasks to test: [list 3-5 key tasks]"
- 5Paste the prompt into your preferred AI tool, like ChatGPT or Claude
- 6Review and customize: Adjust scripts to match your tone and brand
- 7Practice: Read through the script before your first test
- 8Refine after pilot: Update script based on first 1-2 test sessions
Pro Tips
- • Keep tasks realistic: Frame tasks with real motivations, not "Click the button"
- • Practice think-aloud: Demonstrate what you mean by "thinking aloud" in the intro
- • Don't over-script: Use the script as a guide, not a rigid checklist
- • Time-box tasks: If someone is stuck for 2+ minutes, provide a hint and move on
- • Stay neutral: Never defend the design or explain how things "should" work
- • Embrace silence: Pauses are OK - give participants time to think
- • Take good notes: Capture direct quotes and specific observations, not just "it was confusing"

