tool-design-sprint-map-and-target

Name: tool-design-sprint-map-and-target
Author: product-on-purpose

486stars64forks

How to install tool-design-sprint-map-and-target?

product-on-purpose/pm-skills/tool-design-sprint-map-and-target

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

Installs into the current project.

Summary

Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target mo

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 Map and Target (Monday)
4
5	Produce Monday's bundled artifact: the long-term goal that names success in 1-5 years; 3-7 sprint questions converting team fears into testable risks; a 5-15 step customer or system map from key player to outcome; expert interview notes from cameo experts run in parallel; HMW (How Might We) clusters synthesized from the team; and the Decider's chosen target moment. Monday's output becomes Tuesday's design target.
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 1 of the Design Sprint and the brief is locked (via `tool-design-sprint-brief`).
12	- The team is together (in-person, remote, or hybrid) for the full Monday workshop.
13	- Expert interviews are scheduled for Monday afternoon (cameo role; 15-30 minutes each).
14	- The team needs to converge from "five days of work ahead" to "this specific target moment is what we're prototyping."
15
16	## When NOT to Use
17
18	- The brief is not locked. Return to `tool-design-sprint-brief`; without sprint questions, this skill has nothing to converge toward.
19	- The challenge is so broad that "long-term goal" would be longer than 5 years. Return to problem framing.
20	- The team is missing the Decider. The target-moment selection at the end of Monday is the Decider's call; without that call the team disperses Tuesday with no agreed direction.
21	- The team has already pre-decided the target moment. Monday's value is in the convergence; if it's been pre-decided, Monday becomes ratification theater.
22
23	## What This Skill Produces
24
25	A single bundled artifact with six sections:
26
27	1. Long-term goal: one sentence naming success in 1-5 years. Aspirational; cannot be hit in this sprint, but should be visible from the target moment.
28	2. Sprint questions: 3-7 questions converting team fears into testable risks. Phrased as "Can we... ?" or "Will... ?" or "How... ?"; NOT phrased as solutions.
29	3. Customer or system map: 5-15 step flow from key player(s) at the left to outcome (long-term goal) at the right. Includes major actors, decision points, and current alternatives.
30	4. Expert interview notes: synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Surfaced as HMW candidates for the cluster board.
31	5. HMW cluster board: 30-100+ How Might We notes from the team, clustered into 4-8 themes; voted with `tool-note-and-vote` heat-map mechanic to surface top clusters.
32	6. Target moment: the single point on the map (or a tight cluster of points) the Decider picks as the prototyping target. Wednesday's storyboard begins from here.
33
34	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Monday artifact.
35
36	## Inference Inputs
37
38	\| Input \| What the skill does with it \|
39	\|---\|---\|
40	\| Sprint brief (from `tool-design-sprint-brief`) \| Pulls the locked sprint questions as seed for refinement; pulls the challenge statement as the long-term goal seed; pulls the team roster for role assignments in note-and-vote \|
41	\| Existing research \| Used to draft the customer or system map; researcher walks the team through key findings during the map step \|
42	\| Analytics \| Quantitative grounding for the map's decision-point branch points and abandonment moments \|
43	\| Customer examples \| Concrete stories used to validate the map's key player and surface map-step gaps \|
44	\| Expert interview transcripts (run during Monday) \| Synthesized into HMW candidates by the moderator (typically PM or researcher) during the afterno

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Map and Target (Monday)

Produce Monday's bundled artifact: the long-term goal that names success in 1-5 years; 3-7 sprint questions converting team fears into testable risks; a 5-15 st

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

CategoryDesign

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

tool-design-sprint-map-and-target

486stars64forks

View on GitHub

How to install tool-design-sprint-map-and-target?

product-on-purpose/pm-skills/tool-design-sprint-map-and-target

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

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 Map and Target (Monday)
4
5	Produce Monday's bundled artifact: the long-term goal that names success in 1-5 years; 3-7 sprint questions converting team fears into testable risks; a 5-15 step customer or system map from key player to outcome; expert interview notes from cameo experts run in parallel; HMW (How Might We) clusters synthesized from the team; and the Decider's chosen target moment. Monday's output becomes Tuesday's design target.
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 1 of the Design Sprint and the brief is locked (via `tool-design-sprint-brief`).
12	- The team is together (in-person, remote, or hybrid) for the full Monday workshop.
13	- Expert interviews are scheduled for Monday afternoon (cameo role; 15-30 minutes each).
14	- The team needs to converge from "five days of work ahead" to "this specific target moment is what we're prototyping."
15
16	## When NOT to Use
17
18	- The brief is not locked. Return to `tool-design-sprint-brief`; without sprint questions, this skill has nothing to converge toward.
19	- The challenge is so broad that "long-term goal" would be longer than 5 years. Return to problem framing.
20	- The team is missing the Decider. The target-moment selection at the end of Monday is the Decider's call; without that call the team disperses Tuesday with no agreed direction.
21	- The team has already pre-decided the target moment. Monday's value is in the convergence; if it's been pre-decided, Monday becomes ratification theater.
22
23	## What This Skill Produces
24
25	A single bundled artifact with six sections:
26
27	1. Long-term goal: one sentence naming success in 1-5 years. Aspirational; cannot be hit in this sprint, but should be visible from the target moment.
28	2. Sprint questions: 3-7 questions converting team fears into testable risks. Phrased as "Can we... ?" or "Will... ?" or "How... ?"; NOT phrased as solutions.
29	3. Customer or system map: 5-15 step flow from key player(s) at the left to outcome (long-term goal) at the right. Includes major actors, decision points, and current alternatives.
30	4. Expert interview notes: synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Surfaced as HMW candidates for the cluster board.
31	5. HMW cluster board: 30-100+ How Might We notes from the team, clustered into 4-8 themes; voted with `tool-note-and-vote` heat-map mechanic to surface top clusters.
32	6. Target moment: the single point on the map (or a tight cluster of points) the Decider picks as the prototyping target. Wednesday's storyboard begins from here.
33
34	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Monday artifact.
35
36	## Inference Inputs
37
38	\| Input \| What the skill does with it \|
39	\|---\|---\|
40	\| Sprint brief (from `tool-design-sprint-brief`) \| Pulls the locked sprint questions as seed for refinement; pulls the challenge statement as the long-term goal seed; pulls the team roster for role assignments in note-and-vote \|
41	\| Existing research \| Used to draft the customer or system map; researcher walks the team through key findings during the map step \|
42	\| Analytics \| Quantitative grounding for the map's decision-point branch points and abandonment moments \|
43	\| Customer examples \| Concrete stories used to validate the map's key player and surface map-step gaps \|
44	\| Expert interview transcripts (run during Monday) \| Synthesized into HMW candidates by the moderator (typically PM or researcher) during the afterno

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Map and Target (Monday)

Produce Monday's bundled artifact: the long-term goal that names success in 1-5 years; 3-7 sprint questions converting team fears into testable risks; a 5-15 st

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

CategoryDesign

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type