tool-design-sprint-test-and-score

Name: tool-design-sprint-test-and-score
Author: product-on-purpose

486stars64forks

How to install tool-design-sprint-test-and-score?

product-on-purpose/pm-skills/tool-design-sprint-test-and-score

$npx -y skills add product-on-purpose/pm-skills --skill tool-design-sprint-test-and-score

Installs into the current project.

Summary

Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by customers), observed patterns, hot takes from each team member, and the Decider summary (

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2
3	# Design Sprint Test and Score (Friday)
4
5	Friday is the sprint's payoff. 5 target-profile customers run the prototype while the team observes; the team synthesizes observations into a scorecard against the sprint questions; the Decider makes the build / iterate / pivot / stop call by end-of-day. The week's 35-40 person-days plus customer recruiting cost converts into one actionable decision.
6
7	Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This skill is a member of `design-sprint-skills`.
8
9	## When to Use
10
11	- It is Day 5 of the Design Sprint and Thursday's prototype passed trial run.
12	- 5 confirmed participants are scheduled (canonical; or 4 if 1 cancelled-and-no-buffer; pause if below 4).
13	- The team can observe interviews live (in-person or via Zoom breakout room) and synthesize during the day.
14	- The Decider is present Friday PM for the post-interview review (canonically 14:00-18:00 PT window covering observation of slots 4-5 plus Decider review by 17:30 PT).
15
16	## When NOT to Use
17
18	- Thursday prototype did not pass trial run. Re-run trial; if still failing at 19:00 PT Thursday, postpone Friday.
19	- Fewer than 3 customers confirmed. Per Ratified Decision 3, the canonical guidance is 5 customers; 3-4 or 6-7 gets a documented warning; below 3 or above 7 should trigger a re-decision (postpone or split testing). Note: the v0.1.0 family validator does NOT mechanically enforce these thresholds (cohort count is in the EXAMPLE artifact, not in frontmatter); enforcement is a v2.16 validator-expansion candidate.
20	- Decider unavailable for the post-interview review window. Without Decider, the day produces observations without a call.
21	- The team plans to use this skill to write the executive memo. Per Ratified Decision 4: exec memo authoring is delegated to `foundation-stakeholder-update` (existing pm-skills foundation skill); this skill produces the Decider summary only.
22
23	## What This Skill Produces
24
25	A single bundled artifact with six sections:
26
27	1. Per-customer interview observation notes: one section per customer; covers Context (Act 2) reactions, Tasks (Act 4) behavior with timestamps, Debrief (Act 5) reactions including pricing. Captured live during the day's interviews.
28	2. Best quotes: 5-15 verbatim customer quotes the team flags as most signal-bearing. Used in the Decider summary and in any downstream pitch or planning artifact.
29	3. Scorecard grid: rows are the sprint questions (from Monday); columns are the 5 customers; each cell is Y / N / partial / unclear with a one-line note; rightmost column is the team's day-end decision per question (Validated / Invalidated / Inconclusive).
30	4. Observed patterns: 4 buckets (worked, hesitated, broke trust, unexpected) with 2-4 patterns per bucket. Each pattern names how many customers showed it.
31	5. Hot takes: one short paragraph per team member capturing their personal read on Friday before group synthesis biases the read. Written silently in parallel.
32	6. Decider summary: the Decider's call (build / iterate / pivot / stop / reframe) plus the highest-confidence learning, the most important revision the team would make to the prototype direction, and the next artifact the team will produce (the post-sprint deliverable).
33
34	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Friday artifact.
35
36	## Frida

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Test and Score (Friday)

Friday is the sprint's payoff. 5 target-profile customers run the prototype while the team observes; the team synthesizes observations into a scorecard against

Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This

Repoproduct-on-purpose/pm-skills

LicenseApache-2.0

TypeSkills

CategoryTesting

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

tool-design-sprint-test-and-score

486stars64forks

View on GitHub

How to install tool-design-sprint-test-and-score?

product-on-purpose/pm-skills/tool-design-sprint-test-and-score

$npx -y skills add product-on-purpose/pm-skills --skill tool-design-sprint-test-and-score

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2
3	# Design Sprint Test and Score (Friday)
4
5	Friday is the sprint's payoff. 5 target-profile customers run the prototype while the team observes; the team synthesizes observations into a scorecard against the sprint questions; the Decider makes the build / iterate / pivot / stop call by end-of-day. The week's 35-40 person-days plus customer recruiting cost converts into one actionable decision.
6
7	Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This skill is a member of `design-sprint-skills`.
8
9	## When to Use
10
11	- It is Day 5 of the Design Sprint and Thursday's prototype passed trial run.
12	- 5 confirmed participants are scheduled (canonical; or 4 if 1 cancelled-and-no-buffer; pause if below 4).
13	- The team can observe interviews live (in-person or via Zoom breakout room) and synthesize during the day.
14	- The Decider is present Friday PM for the post-interview review (canonically 14:00-18:00 PT window covering observation of slots 4-5 plus Decider review by 17:30 PT).
15
16	## When NOT to Use
17
18	- Thursday prototype did not pass trial run. Re-run trial; if still failing at 19:00 PT Thursday, postpone Friday.
19	- Fewer than 3 customers confirmed. Per Ratified Decision 3, the canonical guidance is 5 customers; 3-4 or 6-7 gets a documented warning; below 3 or above 7 should trigger a re-decision (postpone or split testing). Note: the v0.1.0 family validator does NOT mechanically enforce these thresholds (cohort count is in the EXAMPLE artifact, not in frontmatter); enforcement is a v2.16 validator-expansion candidate.
20	- Decider unavailable for the post-interview review window. Without Decider, the day produces observations without a call.
21	- The team plans to use this skill to write the executive memo. Per Ratified Decision 4: exec memo authoring is delegated to `foundation-stakeholder-update` (existing pm-skills foundation skill); this skill produces the Decider summary only.
22
23	## What This Skill Produces
24
25	A single bundled artifact with six sections:
26
27	1. Per-customer interview observation notes: one section per customer; covers Context (Act 2) reactions, Tasks (Act 4) behavior with timestamps, Debrief (Act 5) reactions including pricing. Captured live during the day's interviews.
28	2. Best quotes: 5-15 verbatim customer quotes the team flags as most signal-bearing. Used in the Decider summary and in any downstream pitch or planning artifact.
29	3. Scorecard grid: rows are the sprint questions (from Monday); columns are the 5 customers; each cell is Y / N / partial / unclear with a one-line note; rightmost column is the team's day-end decision per question (Validated / Invalidated / Inconclusive).
30	4. Observed patterns: 4 buckets (worked, hesitated, broke trust, unexpected) with 2-4 patterns per bucket. Each pattern names how many customers showed it.
31	5. Hot takes: one short paragraph per team member capturing their personal read on Friday before group synthesis biases the read. Written silently in parallel.
32	6. Decider summary: the Decider's call (build / iterate / pivot / stop / reframe) plus the highest-confidence learning, the most important revision the team would make to the prototype direction, and the next artifact the team will produce (the post-sprint deliverable).
33
34	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Friday artifact.
35
36	## Frida

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Test and Score (Friday)

Friday is the sprint's payoff. 5 target-profile customers run the prototype while the team observes; the team synthesizes observations into a scorecard against

Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This

Repoproduct-on-purpose/pm-skills

LicenseApache-2.0

TypeSkills

CategoryTesting

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type