design-5-act-user-interview-testing

Conduct 5-act usability interviews and build color-coded prototype test scorecards.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/coreyone/software-maestro --skill design-5-act-user-interview-testing-coreyone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-5-act-user-interview-testing
Source: https://github.com/coreyone/software-maestro/tree/main/design/evaluation-and-quality/design-5-act-user-interview-testing
Command: npx skills add https://github.com/coreyone/software-maestro --skill design-5-act-user-interview-testing-coreyone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Design sprint teams need unbiased, empirical customer evidence on Friday to decide whether a prototype answers Monday's sprint questions, but unstructured interviews introduce confirmation bias and produce vague conclusions. ## Core Features & Use Cases - 5-Act Interview Protocol: Run five 60-minute 1-on-1 interviews following Michael Margolis's structured script (Welcome, Context, Introduce Prototype, Tasks & Nudges, Debrief) with neutral, non-leading probing prompts. - Pattern Scorecard Matrix: Populate a color-coded scorecard (Green = Validated, Red = Friction, Yellow = Mixed) across all test steps to detect high-confidence patterns from 5 users. - Sprint Question Verdicts: Rate each of Monday's 3 Sprint Questions as Validated, Invalidated, or Inconclusive with verbatim quotes, then issue a Go / Pivot / Kill recommendation. - Use Case: After building a rapid prototype facade on Thursday, run five customer interviews on Friday and deliver an evidence-backed scorecard that tells product leadership whether to proceed, pivot pricing, or kill the concept. ## Quick Start Run the Friday 5-act user interview testing for our sprint prototype and synthesize the pattern scorecard with verdicts for our 3 sprint questions.

Frequently Asked Questions about design-5-act-user-interview-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a 5-act user interview for a design sprint?▼

Run five 60-minute 1-on-1 interviews following the 5-act structure: friendly welcome, context questions about current workflows, prototype introduction with a scenario, task observation with neutral think-aloud prompts, and a quick debrief covering value and pricing.

How many users do I need for usability testing in a design sprint?▼

Five users is the standard, based on Jakob Nielsen's 5-user rule showing that five participants uncover roughly 85% of usability and concept flaws. This makes five interviews sufficient for detecting high-confidence patterns in a sprint.

What is a pattern scorecard in prototype testing?▼

A pattern scorecard is a color-coded matrix where each observation per test step is marked green for validated, red for friction or rejection, and yellow for mixed signals. Scanning columns vertically across five users reveals which prototype steps work and which fail.

When should I not use 5-act interview testing?▼

Do not use it for automated headless browser tests, quantitative A/B experimentation analytics, or storyboarding and prototyping work. It is designed specifically for live qualitative interviews on an existing interactive prototype.

How do I avoid confirmation bias in user interviews?▼

Use neutral, non-directive probing prompts such as asking what the participant expected to happen, never defend or explain the prototype, and never ask leading questions. The 5-act protocol structures each phase to keep interviewer bias out of the evidence.