Script

Script

Note

Source alignment: reflects the script guidance on consistent, open‑ended, objective, and goal‑oriented questions, plus the near‑verbatim opening checklist from the “Finish building a research plan: Script” reading.

Design the script to be consistent across sessions yet flexible enough to uncover why users behave a certain way.

Structure

• Opening
  • Welcome and rapport building; explain purpose: you are testing the design, not the person.
  • Consent: describe recording, data use, storage, and the right to stop at any time.
  • Privacy: reassure that identifying details will be removed from notes/clips.
  • Think‑aloud request: ask participants to say what they expect and what surprises them.
  • Basics: optionally collect name (or alias), general background relevant to the product (e.g., role, context of use).
• Tasks
  • Prompts map to research goals and questions; one primary goal per task.
  • Observe behaviors (navigation, hesitation, backtracks), not just outcomes.
  • Use neutral probes to understand reasoning without leading.
• Wrap‑up
  • Quick reflections: what worked, what was confusing, what they would improve first.
  • Overall ease, confidence, and likelihood to use/recommend.

Good Questions Are

• Consistent: read verbatim; avoid rephrasing that changes meaning.
• Open‑ended: encourage explanation and alternatives beyond yes/no.
• Objective: avoid implying a correct answer or path.
• Goal‑oriented: each maps to a goal/RQ and intended observation/KPI.

Moderator Practices

• Encourage elaboration: “What makes you say that?” “What were you expecting there?”
• Be flexible in follow‑ups to reveal mental models without steering.
• Follow the participant’s lead when new relevant topics emerge; timebox detours.
• Maintain privacy; never reference other participants or prior sessions.
• Keep a calm demeanor; avoid verbal/non‑verbal cues that signal correctness.

Task Design Tips

• Specific and action‑oriented: “Book a morning yoga session for Tuesday.”
• No clues: avoid using on‑screen labels (e.g., don’t say the exact button text).
• One objective per task; avoid multi‑goal prompts that complicate analysis.
• Define success/failure and assistance ahead of time; set timeouts where needed.
• Plan follow‑ups: short, neutral probes to explore why without steering the path.

Opening Script (Example)

• Welcome and thanks; explain purpose and think‑aloud.
• Confirm consent; start recording if applicable.
• Context: “We’ll look at a prototype; some parts may not work yet.”
• Remind: “There are no right or wrong answers; your feedback helps improve the design.”

Task Prompts (Examples)

• “Find and enroll in a beginner class that fits your schedule.”
• “Change your enrollment to a different time.”
• “Locate where to update your notification preferences.”

Begin Interview Checklist

• Welcome and rapport + quick warm‑up question.
• Consent and privacy; explain recording and data handling.
• Basics: confirm device, context of use, any AT in use.
• Remind think‑aloud and voluntary participation; invite breaks and questions.

Begin Interview (Near‑source checklist)

• Welcome and thank participants; build rapport with a simple warm‑up.
• If observed or recorded, ask for consent beforehand.
• Ask for basic information (e.g., name, age, occupation) if needed for context.
• Reassure participants the interview is not a test; there are no “right” answers.
• Remind participants to think out loud throughout the session.
• Set expectations around what works and what doesn’t in the prototype.
• Be open and transparent: invite questions, clarify as needed, offer breaks.
• Explain why you’re collecting this data and how it will be used.
• Assure participants their privacy will be respected and identifying details will be scrubbed from recordings/notes.

Note

Pilot the script with 1–2 people to validate clarity, pacing, and difficulty. Adjust wording, order, and time estimates before full recruitment.

Summary: A disciplined script standardizes sessions while allowing natural exploration. Keep prompts neutral, tie each to goals, and protect participants’ privacy from the first sentence to the last.