# Design Sprint Plan: [Sprint Name]

**Challenge:** [One sentence describing the problem to solve]
**Dates:** [Monday] — [Friday]
**Facilitator:** [Name]
**Decider:** [Name]
**Location:** [Room / Remote tool]

---

## Sprint Team

| Name | Role | Expertise |
|------|------|-----------|
| [Name] | Decider | [Area] |
| [Name] | Facilitator | [Area] |
| [Name] | Designer | [Area] |
| [Name] | Engineer | [Area] |
| [Name] | Domain expert | [Area] |
| [Name] | [Role] | [Area] |

---

## Pre-Sprint Checklist

| Task | Owner | Status |
|------|-------|--------|
| Book room for full week (10am-5pm) | [ ] | [ ] Done |
| Recruit 5 test participants for Friday | [ ] | [ ] Done |
| Gather materials (whiteboards, markers, stickies, dot stickers, paper, timer) | [ ] | [ ] Done |
| Block team calendars (no meetings during sprint) | [ ] | [ ] Done |
| Prepare background brief for team (problem context, data, user research) | [ ] | [ ] Done |
| Identify 2-4 experts for Monday afternoon interviews | [ ] | [ ] Done |
| Set up prototype tool (Figma file, Keynote, etc.) | [ ] | [ ] Done |
| Prepare snacks and lunch plan | [ ] | [ ] Done |
| Share sprint rules with team (no devices, no side meetings) | [ ] | [ ] Done |

---

## Monday: Map

### Long-Term Goal
> [If everything goes perfectly, what's true in 2 years?]

### Sprint Questions
1. Can we [question]?
2. Will [users] [behavior]?
3. Is [assumption] true?

### Problem Map
[Photo of whiteboard map — actors on left, goal on right, steps in between]

### Expert Interviews

| Expert | Area | Key Insights |
|--------|------|-------------|
| [Name] | [Area] | [Notes] |
| [Name] | [Area] | [Notes] |
| [Name] | [Area] | [Notes] |

### How Might We Notes (Top Voted)
1. HMW [question]? ([#] votes)
2. HMW [question]? ([#] votes)
3. HMW [question]? ([#] votes)

### Target
> We're focusing on: [specific area of the map]

---

## Tuesday: Sketch

### Lightning Demos

| Presenter | Product/Example | Big Idea |
|-----------|----------------|----------|
| [Name] | [Example] | [Takeaway] |
| [Name] | [Example] | [Takeaway] |
| [Name] | [Example] | [Takeaway] |

### Solution Sketches
[Photos of each person's three-panel solution sketch — stored in project folder]

- Sketch 1: [Brief description] by [Name]
- Sketch 2: [Brief description] by [Name]
- Sketch 3: [Brief description] by [Name]
- Sketch 4: [Brief description] by [Name]
- Sketch 5: [Brief description] by [Name]

---

## Wednesday: Decide

### Heat Map Results
[Photo of sketches with dot stickers — which parts got the most attention?]

### Speed Critique Notes

| Sketch | Standout Ideas | Concerns |
|--------|---------------|----------|
| Sketch 1 | [Ideas] | [Concerns] |
| Sketch 2 | [Ideas] | [Concerns] |
| Sketch 3 | [Ideas] | [Concerns] |

### Straw Poll
- [Name]: voted for [Sketch/Part]
- [Name]: voted for [Sketch/Part]
- [Name]: voted for [Sketch/Part]

### Decider's Decision
> We're prototyping: [Description of chosen direction]

> Reason: [Why this direction]

### Storyboard
[Photo of storyboard on whiteboard — ~10-15 frames showing the test flow]

---

## Thursday: Prototype

### Team Roles

| Role | Person |
|------|--------|
| Maker 1 | [Name] — [What they're building] |
| Maker 2 | [Name] — [What they're building] |
| Stitcher | [Name] |
| Writer | [Name] |
| Asset collector | [Name] |
| Interview prep | [Name] |

### Prototype Tool
[Figma / Keynote / HTML / Other]

### Prototype Link
[Link to prototype]

### End-of-Day Run-Through
- [ ] Full flow works without breaking
- [ ] Copy is realistic (no lorem ipsum)
- [ ] Key decision points are clear
- [ ] Prototype covers the test scenarios

---

## Friday: Test

### Participant Schedule

| Time | Participant | Screener Match |
|------|-----------|---------------|
| 9:00-10:00 | Participant 1: [Name/Code] | [Key characteristic] |
| 10:15-11:15 | Participant 2: [Name/Code] | [Key characteristic] |
| 11:30-12:30 | Participant 3: [Name/Code] | [Key characteristic] |
| 1:30-2:30 | Participant 4: [Name/Code] | [Key characteristic] |
| 2:45-3:45 | Participant 5: [Name/Code] | [Key characteristic] |

### Interview Script Outline
1. **Warm-up** (5 min): [Questions about background]
2. **Context** (10 min): [Questions about current behavior]
3. **Prototype walkthrough** (35 min): [Task prompts]
4. **Debrief** (10 min): [Overall impression questions]

### Observation Notes

| | P1 | P2 | P3 | P4 | P5 | Pattern |
|--|----|----|----|----|----|----|
| [Key moment 1] | | | | | | |
| [Key moment 2] | | | | | | |
| [Key moment 3] | | | | | | |
| [Key moment 4] | | | | | | |
| [Key moment 5] | | | | | | |

Use: 🟢 Positive | 🔴 Negative | 🟡 Neutral | Write brief notes in each cell

### Patterns Summary

| Pattern | Strength (x/5) | Action |
|---------|----------------|--------|
| [Pattern] | [#]/5 users | [Keep / Change / Investigate] |
| [Pattern] | [#]/5 users | [Keep / Change / Investigate] |
| [Pattern] | [#]/5 users | [Keep / Change / Investigate] |

---

## Sprint Decision

**Decision:** [ ] Go — build it | [ ] No-go — pivot | [ ] Go with changes

**Reasoning:**
> [Why this decision, based on what was observed]

**Sprint Questions Answered:**
1. [Question] → [Answer from testing]
2. [Question] → [Answer from testing]
3. [Question] → [Still unclear — needs more research]

---

## Next Steps

| Action | Owner | Due |
|--------|-------|-----|
| Share results with broader team | [Name] | [Date] |
| Break solution into user stories | [Name] | [Date] |
| Address open questions from testing | [Name] | [Date] |
| Sprint retro (process improvement) | [Name] | [Date] |
| Archive sprint artifacts | [Name] | [Date] |
