# Design Sprint Monday Artifact: [Initiative or Challenge name]

<!-- Monday Map and Target bundled artifact. Captures the team's Day 1 convergence from sprint questions to target moment. Tuesday's sketches begin from the target moment. -->

## Long-Term Goal

[One sentence. 1-5 years out. Aspirational. Names the success state the team is sprinting toward, not the sprint output itself.]

## Sprint Questions

[3-7 questions converting team fears into testable risks. Phrased as "Can we... ?", "Will... ?", or "How... ?"; NOT phrased as solutions. The brief's locked sprint questions seed this list; the team refines and adds during the morning.]

1. [Question 1]
2. [Question 2]
3. [Question 3]
4. [Question 4]
5. [Question 5]

## Customer or System Map

```
[Key Player] --> [Step 1] --> [Step 2] --> [Step 3 (decision point)] --+--> [Step 4a] --> [...]
                                                                       |
                                                                       +--> [Step 4b] --> [...]
                                                                            (current alternative)
                                                                                    |
                                                                                    v
                                                                            [Long-term goal end state]
```

[5-15 step flow from Key Player on the left to the Long-Term Goal end state on the right. Include major actors, decision points, and current alternatives (the "do nothing" or competitor path). Use the whiteboard structure; render the final map as ASCII or describe in 3-5 sentences.]

**Key player:** [Who is at the leftmost node? Cross-checked with the brief's target customer.]

**Map narrative:** [3-5 sentences walking the reader through the map: who starts where, what major decisions they make, where they currently abandon or substitute, and where they would land if the long-term goal succeeded.]

## Expert Interview Notes

[Synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Each expert gets a sub-section.]

### Expert 1: [Name, role, why-they-were-invited]

- [Observation 1]
- [Observation 2]
- [HMW candidate surfaced]

### Expert 2: [Name, role, why-they-were-invited]

- [Observation 1]
- [Observation 2]
- [HMW candidate surfaced]

### Expert 3: [Name, role, why-they-were-invited]

- [Observation 1]
- [Observation 2]
- [HMW candidate surfaced]

## HMW Cluster Board

[Total HMWs surfaced during morning + expert interviews; clustered into 4-8 themes; heat-map voted via `tool-note-and-vote`. Show top 4-6 clusters with vote totals.]

| Cluster | Theme | HMW count | Heat-map votes |
|---|---|---|---|
| C1 | [Theme name] | [N HMWs] | [V votes] |
| C2 | [Theme name] | [N HMWs] | [V votes] |
| C3 | [Theme name] | [N HMWs] | [V votes] |
| C4 | [Theme name] | [N HMWs] | [V votes] |

**Top cluster HMWs (verbatim, 3-5 per top cluster):**

**C1: [Theme]**
- HMW [verbatim]
- HMW [verbatim]
- HMW [verbatim]

**C2: [Theme]**
- HMW [verbatim]
- HMW [verbatim]
- HMW [verbatim]

## Target Moment

[The single point on the map (or tight cluster of points) the Decider picks. Tuesday's sketches and Wednesday's storyboard begin from here. Render as a circled position on the map narrative + a 1-3 sentence rationale.]

**Selected target:** [Map position; e.g., "Step 3 (Decision point: capture or skip)" or "Step 2 plus Step 5 (capture moment plus first recall surface)"]

**Decider rationale:** [Why this point, why not the alternatives, what assumption the team is choosing to test through prototyping here.]

**Sprint questions the target moment most directly tests:** [Reference question numbers from the Sprint Questions section above; usually 1-2 of the 3-7.]

## Decider Checkpoint

**Decider sign-off required before Tuesday begins.**

- [ ] Decider confirms the long-term goal (1-5 years out; aspirational).
- [ ] Decider confirms the final sprint questions (3-7; converted from fears to testable risks).
- [ ] Decider acknowledges the customer or system map represents the team's shared understanding (not "the truth"; the prototype Friday will adjust this understanding).
- [ ] Decider confirms the top HMW clusters from the heat-map vote (those clusters orient Wednesday's heat-map).
- [ ] Decider selects the target moment and accepts that Tuesday's sketches will be drawn against this target (and not, by default, against the un-selected clusters).
- [ ] Decider commits to attending Wednesday morning for heat-map plus supervote (the load-bearing Wednesday window from the brief).

**Signed:** [Decider name, role], [ISO date and local time]
