tool-design-sprint-test-and-score

Synthesizes Design Sprint Friday customer interviews into a scorecard and Decider call.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-test-and-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-design-sprint-test-and-score
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-test-and-score
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-test-and-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Day 5 of a Design Sprint generates hours of raw customer interview observations, and teams often leave without a clear, evidence-backed decision. This Skill structures Friday's synthesis so the sprint closes with a documented build, iterate, pivot, or stop call instead of ambiguous notes.

Core Features & Use Cases

  • Bundled Friday Artifact: Produces per-customer observation notes, best quotes, a scorecard grid mapping sprint questions against customers, observed patterns in four buckets, silent hot takes, and a Decider summary.
  • Scorecard Mechanic: Applies explicit day-end decision rules (Validated, Invalidated, Inconclusive) based on Y/N/partial counts across the 5-customer cohort, with Decider override reasoning.
  • Decider Checkpoint: Ends with a signed checkpoint capturing the call, highest-confidence learning, most important revision, and the next artifact with an owner.
  • Use Case: After Thursday's prototype passes trial run, run five 50-60 minute customer interviews, then use this Skill to synthesize observations into the scorecard and capture the Decider's build call plus the follow-up PRD assignment.

Quick Start

Use the design sprint test-and-score skill to synthesize today's five customer interviews into a scorecard and Decider summary for our prototype.

Frequently Asked Questions about tool-design-sprint-test-and-score

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

FAQPage Schema
How do I run Day 5 of a Design Sprint?

Run five 50-60 minute customer interviews against Thursday's prototype while the team observes, then synthesize observations into a scorecard grid, pattern buckets, and silent hot takes. The Decider closes the day with a build, iterate, pivot, or stop call.

How many customers should a design sprint test with?

The canonical cohort is 5 customers, based on Nielsen Norman Group research showing pattern confidence inflects at that size. Cohorts of 3-4 or 6-7 get a documented warning; below 3 or above 7 should trigger postponing or splitting the test.

What is a design sprint scorecard grid?

A scorecard grid maps sprint questions as rows against customers as columns, with each cell marked Y, N, partial, or unclear. A day-end decision column marks each question Validated, Invalidated, or Inconclusive based on the count pattern.

When should I not run the Friday sprint test?

Skip it if Thursday's prototype failed trial run, fewer than 3 customers are confirmed, or the Decider cannot attend the post-interview review. Without a Decider the day produces observations but no actionable call.

What happens after the design sprint Decider call?

The Decider summary names the next artifact: a PRD via deliver-prd for a build call, an experiment design for iterate, a pivot rationale for pivot, or a stakeholder update. Executive memos are delegated to the foundation-stakeholder-update skill.