skills.rest
product-on-purpose
product-on-purposeOFFICIAL
Explore all skills by this author →
GitHub

tool-design-sprint-map-and-target

Facilitates Design Sprint Day 1 to produce long-term goal, sprint questions, customer map, HMW clusters, and target moment.

640|81|Updated Jan 9, 2026
Search Tags:#facilitation#workshop#design sprint#hmw#customer map#target moment#sprint questions
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-design-sprint-map-and-target
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-map-and-target
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design Sprint teams often start Monday without a structured way to converge from a broad challenge to a single prototyping target, resulting in scattered Tuesday sketches and no shared direction. This Skill guides the full Day 1 (Monday) workshop so the team produces one bundled artifact containing the long-term goal, sprint questions, customer or system map, expert interview notes, HMW cluster board, and the Decider's chosen target moment.

Core Features & Use Cases

  • Bundled Monday Artifact: Produces six sections in one document: long-term goal (1-5 years), 3-7 testable sprint questions, a 5-15 step customer or system map, expert interview notes, a heat-map-voted HMW cluster board, and the Decider's target moment.
  • Structured Monday Agenda: Provides a timed facilitation plan (09:00-17:00) covering goal setting, map drafting, cameo expert interviews, HMW clustering via note-and-vote, and Decider target selection within a 105-minute facilitated timebox.
  • Decider Checkpoint: Ends with a sign-off checklist confirming the goal, questions, map, top HMW clusters, and target moment before Tuesday's sketches begin.
  • Use Case: A product team kicking off a 5-day Design Sprint uses this Skill on Monday morning with a locked sprint brief, runs three cameo expert interviews in the afternoon, clusters 67 HMW notes into 6 themes, and ends the day with the Decider selecting the capture-plus-confirmation moment as the prototyping target.

Quick Start

Run the Design Sprint Monday map-and-target workshop using our locked sprint brief to produce the long-term goal, sprint questions, customer map, HMW clusters, and target moment.

Frequently Asked Questions about tool-design-sprint-map-and-target

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

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

Day 1 (Monday) produces a bundled artifact: a long-term goal, 3-7 sprint questions, a 5-15 step customer or system map, expert interview notes, an HMW cluster board, and the Decider's target moment. The full workshop runs about 7 hours with a 105-minute facilitated synthesis timebox.

What is a target moment in a Design Sprint?▼

The target moment is the single point (or tight cluster of points) on the customer or system map that the Decider selects at the end of Monday. Tuesday's sketches and Wednesday's storyboard are drawn against this target, so without it the team diverges with no shared direction.

What do I need before starting the Design Sprint Monday workshop?▼

You need a locked sprint brief containing the challenge statement, sprint questions, and team roster, plus existing research, analytics, and customer examples. Expert interviews should be scheduled for Monday afternoon, and the Decider must be present for target selection.

How many sprint questions and HMW notes should a Design Sprint produce?▼

Sprint questions should number 3-7, phrased as testable risks like "Can we...?" rather than solutions. HMW notes typically total 30-100+, clustered into 4-8 themes and narrowed by heat-map dot voting to surface the top clusters.

When should I not run the map-and-target workshop?▼

Skip it if the sprint brief is not locked, the Decider is absent, or the team has already pre-decided the target moment. Also avoid it when the challenge is so broad that a long-term goal would exceed a 5-year horizon; return to problem framing first.

Related Skills

Explore More Product & Management Skills→
AX-BD-TeamAX-BD-Team

ax-sprint

Design a 5-day validation sprint from a Brief JSON and generate Validation JSON, checklist, and Confluence page.

Official
Intermediate
paulalarosapaulalarosa

design-sprint

Run a structured 5-day design sprint to prototype and test product ideas with real users.

Community
Intermediate
Maitreya04Maitreya04

design-sprint

Guide teams through a 5-day design sprint to prototype and test ideas with users.

Community
Advanced
Prorise-coolProrise-cool
24

opportunity-solution-tree

Guide product managers through creating an Opportunity Solution Tree.

Community
Advanced