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

<!-- Friday sprint-closing artifact. Captures customer interview observations, scorecard, patterns, hot takes, and the Decider's call. The week's payoff. -->

## Per-Customer Interview Observation Notes

### Customer 1: [Anonymized ID] (slot [time])

**Profile summary:** [Demographics + relevance to target profile; pre-screen score if applicable]

**Context (Act 2) reactions:**
- [Behavior or quote 1]
- [Behavior or quote 2]
- [Behavior or quote 3]

**Tasks (Act 4) behavior:**
- **Task 1:** [Behavioral observations with timestamps where relevant; e.g., "completed Task 1 in 47 seconds; hesitated 6 sec at Panel 3 before tapping the chip"]
- **Task 2:** [Behavioral observations]
- **Task 3:** [Behavioral observations]

**Debrief (Act 5) reactions:**
- [Overall reaction summary]
- [Pricing answer if relevant]
- [Anything-else moments]

### Customer 2: [Anonymized ID] (slot [time])

[Same structure as Customer 1]

### Customer 3: [Anonymized ID] (slot [time])

[...]

### Customer 4: [Anonymized ID] (slot [time])

[...]

### Customer 5: [Anonymized ID] (slot [time])

[...]

## Best Quotes

[5-15 verbatim customer quotes the team flags as most signal-bearing. Format: quote attributed to anonymized customer ID. Selected to inform Decider summary or downstream pitch / planning artifact.]

1. "[Verbatim quote]" - C[N]
2. "[Verbatim quote]" - C[N]
3. "[Verbatim quote]" - C[N]
4. "[Verbatim quote]" - C[N]
5. "[Verbatim quote]" - C[N]
6. "[Verbatim quote]" - C[N]

## Scorecard Grid

Rows: sprint questions from Monday's map-and-target. Columns: 5 customers. Each cell: Y / N / partial / unclear with one-line note. Rightmost column: day-end decision per question.

| | C1 | C2 | C3 | C4 | C5 | Day-end decision |
|---|---|---|---|---|---|---|
| Q1: [Question wording from Monday] | [Y/N/p/u + note] | [...] | [...] | [...] | [...] | [Validated / Invalidated / Inconclusive with N-of-5 reasoning] |
| Q2: [Question wording] | [...] | [...] | [...] | [...] | [...] | [Decision] |
| Q3: [...] | [...] | [...] | [...] | [...] | [...] | [Decision] |
| Q4: [...] | [...] | [...] | [...] | [...] | [...] | [Decision] |
| Q5: [...] | [...] | [...] | [...] | [...] | [...] | [Decision] |
| Q6: [...] | [...] | [...] | [...] | [...] | [...] | [Decision] |

[Decider override notes: if any day-end decision differs from the mechanical rule, the Decider records the reasoning here.]

## Observed Patterns

[4 buckets. Each pattern names how many customers showed it (N of 5).]

### Worked (validated patterns)

- **[Pattern]** (N of 5): [Description; which customers showed it; why this matters.]
- **[Pattern]** (N of 5): [...]

### Hesitated (friction patterns)

- **[Pattern]** (N of 5): [Description; where in the flow hesitation appeared; what the customers said about it.]
- **[Pattern]** (N of 5): [...]

### Broke trust (trust failures)

- **[Pattern]** (N of 5): [Description; what triggered the trust break; whether the customer recovered.]
- **[Pattern]** (N of 5): [...]

### Unexpected (surprising patterns the team did not predict)

- **[Pattern]** (N of 5): [Description; why this is novel; whether it suggests a future opportunity.]
- **[Pattern]** (N of 5): [...]

## Hot Takes

[Each team member writes one short paragraph silently and in parallel before group synthesis. Captures personal read on Friday before consensus bias sets in.]

### [Team member 1 name + role]

[2-4 sentences. Personal read. Strongly opinionated. Specific.]

### [Team member 2 name + role]

[2-4 sentences.]

### [Team member 3 name + role]

[2-4 sentences.]

### [Team member 4 name + role]

[2-4 sentences.]

## Decider Summary

**The call:** [Build / Iterate / Pivot / Stop / Reframe]

**Rationale:** [3-5 sentences explaining the call. Reference scorecard day-end decisions and the most signal-bearing patterns. Acknowledge what the call rules out.]

**Highest-confidence learning from this sprint:** [One sentence stating the thing the team is now most confident about. Should be supported by 4-of-5 or 5-of-5 scorecard evidence.]

**Most important revision the team would make:** [One sentence stating the most important change to the direction. Could be a feature adjustment, an audience adjustment, a positioning adjustment, or a model adjustment.]

**Next artifact:** [The post-sprint deliverable. Examples: "PRD for v0.1 build via deliver-prd"; "smaller follow-on experiment design via measure-experiment-design"; "pivot rationale documented via iterate-pivot-decision"; "stakeholder update via foundation-stakeholder-update".]

## Decider Checkpoint

**Decider sign-off required before the sprint closes.**

- [ ] Decider confirms the scorecard reflects the team's collective read (with override reasoning where applicable).
- [ ] Decider commits to the call (build / iterate / pivot / stop / reframe) and acknowledges the team will not re-litigate without explicit new evidence.
- [ ] Decider names the highest-confidence learning and accepts it as the load-bearing finding of the sprint.
- [ ] Decider names the most important revision and assigns ownership.
- [ ] Decider names the next artifact and the owner who will produce it (canonically within 5 business days of sprint close).
- [ ] Decider acknowledges Monday context handoff: any pre-existing roadmap commitments dependent on the build direction are re-confirmed or revised.

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

**Sprint closed.**
