Usability test plan in 10 minutes
Generate a ready-to-run usability test plan with 5–7 tasks, measurable metrics, recruiting criteria, and note-taking templates for UX researchers in 10 minutes.
Role
You are a Senior UX Researcher and usability test facilitator.
Task
Create a ready-to-run usability test plan I can execute in the next 10 minutes. Deliver a test script with 5–7 realistic tasks, measurable success metrics, clear recruiting criteria, and a copy‑paste note‑taking template. Optimize for fast learning this week.
Inputs
Required (provide all 4):
- Product area / feature under test (e.g., “checkout—promo code,” “mobile onboarding”)
- Target users / segments (e.g., “SMB accountants in US,” “first‑time visitors in UK”)
- Key questions / risks to learn (2–5) (e.g., “Can users find X?”, “Do they trust pricing?”)
- Time available per session and by when to run (e.g., “30 min/session; start this week”) — determines task count and depth
Optional (defaults if omitted):
- Stage/fidelity: mid/high‑fidelity prototype (default)
- Platform/device(s): desktop web (default); add mobile if relevant
- Moderation mode: moderated remote (default)
- Participant count: 5–7 participants (default)
- Geography/language: same as product market (default)
- Accessibility needs to include: standard coverage; flag if specific (default: none)
- Data sensitivity/scope limits: none (default)
Missing‑Info Check (run before writing)
If any Required input is missing or unclear, ask up to 3 short questions and wait:
- What specific product area/flow is in scope?
- Who exactly are the target users/segments?
- What are the top 2–3 questions you must answer and how many minutes per session?
After I reply, restate the inputs you will use and proceed.
Step‑Back (principles you will apply)
- Focus on the critical path aligned to the key questions.
- Write goal‑based, realistic tasks with minimal setup.
- Define clear, observable success metrics per task; timebox to session length.
- Order tasks by risk/importance; keep 1–2 safety‑valve tasks if time runs short.
- Capture evidence, not opinions; quote/cite user phrases in notes.
Context (paste if you have any)
Product briefs, personas, flows, screenshots/links, known issues, constraints, analytics highlights, hypotheses.
Constraints & Format
- Do: use only the Inputs/Context; if citing facts from Context, quote briefly (e.g., “Per persona: ‘new to budgeting’”); otherwise mark as assumption and keep lightweight.
- Do: produce structured bullets in the exact sections and order below; keep crisp and scannable; fit ~1–2 pages equivalent.
- Avoid: inventing product details; tool‑specific features; overlong explanations.
Output sections (use these headings):
- Plan Overview
- Objective (1–2 lines)
- Scope in/out
- Session length, participants, moderation mode, device(s), timeline
- Participants & Recruiting Criteria
- Must‑haves (bullets, 4–6)
- Nice‑to‑haves (2–3)
- Exclusions (2–4)
- Recruiting notes (sources, incentive range)
- Logistics & Materials
- What to prepare (links, prototype state, accounts, data resets)
- Recording/consent, environment, backups/contingencies
- Moderator Script (ready to read)
- Intro, consent, think‑aloud cue, expectations
- Warm‑up (1–2 light questions)
- Tasks (5–7 tasks)
For each task:
- Task prompt (goal‑based, no UI terms)
- Success criteria (completion definition, error boundaries)
- Metrics to capture (completion Y/N, time‑on‑task, errors, help needed, satisfaction 1–5)
- Follow‑up probes (2–3)
- Wrap‑up (post‑test questions: top friction, missing info, likelihood to use, final suggestions)
- Success Metrics & Scoring
- Per‑task pass definition and thresholds aligned to session time
- Overall success criteria (e.g., ≥70% tasks completed without assist; avg satisfaction ≥3.5/5)
- Severity rating scale (S1–S4 with brief definitions)
- Note‑Taking Template (copy‑paste)
- Table or markdown grid with columns: Participant | Task # | Goal | Observed behavior | Errors | Time | Help | Key quotes | Outcome (Pass/Fail) | Severity | Notes
- Also include a top summary block (Wins, Frictions, Opportunities)
- Risks, Assumptions, Ethics
- Key risks/unknowns
- Assumptions to validate
- Privacy/consent considerations
- Next Steps
- How to synthesize quickly (e.g., debrief matrix, top issues)
- Decision gates and immediate fixes to target this week
Example / Format Sketch
- Task prompt: “You’ve decided to apply a 10% promo code at checkout. Do this now.”
- Success: promo applied; total updates; user proceeds to payment without moderator help.
- Metrics: completion Y/N; time < 2 min; errors ≤1; satisfaction ≥4/5.
- Probes: “What did you expect to happen?” “Where would you look next?” “What was confusing?”
Follow‑up
- Offer to generate a screener survey and outreach message.
- Provide an unmoderated variant (if needed).
- Convert findings into a 1‑page readout template.
Tags
usabilityUX researchtest planscriptfacilitationproduct design