# Design Sprint Readiness Assessment: [Initiative or Challenge name]

<!-- One-line description of the challenge the team is considering running a Design Sprint to test. -->

## Inputs Captured

**Challenge description:**

> [The product question, opportunity, or risk the sprint would address, framed as a specific testable challenge.]

**Existing hypothesis (from Foundation Sprint or other source):**

> [The Founding Hypothesis sentence if available, plus the highest-risk assumption flagged in the FS assumption scorecard. If no FS exists, state "no prior hypothesis; sprint will form one Monday" or describe the source.]

**Customer access status:** [Recruiter named or recruiting source identified; estimated days to secure 5 target-profile customers; existing customer base accessible OR external recruiting needed.]

**Decider name and availability:** [Name; full-week availability OR specific windows confirmed; flag any gaps in Monday morning / Wednesday morning / Friday afternoon load-bearing moments.]

**Team composition draft:**

- [Name] ([role]; Decider candidate)
- [Name] ([role; e.g., design lead])
- [Name] ([role; e.g., engineering lead])
- [Name] ([role; e.g., PM or researcher])
- [Name] ([role])

**Prototype medium (proposed):** [Clickable (Figma), slideware (Keynote), service role-play, paper, physical mock, other. With 1-2 sentences on why this medium fits the challenge.]

**(Optional) Logistics constraints:** [Date windows, location, format (in-person / remote / hybrid).]

## Readiness Verdict: **[Go / Conditional Go / Wait]**

[One-sentence summary explaining the verdict.]

| Criterion | Status | Notes |
|---|---|---|
| 1. Challenge is named and sprint-worthy | [PASS / YELLOW / FAIL] | [Notes] |
| 2. Stakes are meaningful | [PASS / YELLOW / FAIL] | [Notes] |
| 3. Decider available for load-bearing moments | [PASS / YELLOW / FAIL] | [Notes] |
| 4. Team size appropriate (4-7) | [PASS / YELLOW / FAIL] | [Notes] |
| 5. Team can clear 5 consecutive days | [PASS / YELLOW / FAIL] | [Notes] |
| 6. Customer access for Friday testing secured | [PASS / YELLOW / FAIL] | [Notes] |
| 7. Prototype medium feasible in 1 day | [PASS / YELLOW / FAIL] | [Notes] |
| 8. Sprint output has a path forward | [PASS / YELLOW / FAIL] | [Notes] |

## Diagnosis

[2-4 paragraphs explaining what is in place, what is missing or weak, and what is uncertain. Be specific about each yellow or failing criterion. If verdict is Go, this section should still surface any risks that justify the Go.]

[If verdict is Conditional Go: name each yellow flag explicitly and describe how it would block the sprint if not addressed.]

[If verdict is Wait: name each failing criterion and describe the prerequisite work the team should do before re-running the diagnostic. Special note on criterion 6 (customer access): if uncertain, default to Wait until recruiter and source are confirmed; 7-10 days of lead time is the canonical minimum.]

## Recommended Preconditions (Conditional Go or Wait only)

[Bulleted list of concrete actions to close gaps. Each precondition has an owner and a target completion date.]

1. **[Precondition]** ([Owner]; deadline: [date]). [Why this matters; what "done" looks like.]
2. **[Precondition]** ([Owner]; deadline: [date]). [Why this matters; what "done" looks like.]

## Customer Recruiting Plan (Go or Conditional Go only)

| Element | Value |
|---|---|
| Target customer profile | [Specific enough to recruit against; e.g., "B2B SaaS PMs at companies 50-500 FTE who have shipped at least one feature in the last 90 days"] |
| Source | [Customer base, panel service, professional network, intercept, paid recruiter] |
| Count needed | 5 (canonical; 6 if one buffer is available for cancellations) |
| Incentive | [Honorarium amount and currency; typical USD 75-150 per 60-minute interview for B2B; USD 25-75 for B2C] |
| Recruiter owner | [Name; responsible for scheduling Friday interview slots] |
| Recruiting deadline | [Date; canonically 7-10 days before Friday testing] |
| Friday scheduling | [Time blocks; canonical 6 customer slots Friday 09:00-15:00 with 1 buffer slot] |

[Add notes on any recruiting risks (e.g., target segment is hard to reach; channel is saturated; honorarium budget not yet approved).]

## Recommended Pre-Sprint Activities (Go or Conditional Go only)

[Bulleted list of prep tasks to complete in the days before Monday.]

1. **[Activity]** ([Owner]; deadline: [date]). [What and why.]
2. **[Activity]** ([Owner]; deadline: [date]). [What and why.]
3. **[Activity]** ([Owner]; deadline: [date]). [What and why.]
4. **[Activity]** ([Owner]; deadline: [date]). [What and why.]

## Recommended Attendees (Go or Conditional Go only)

| Attendee | Role | Required for which days |
|---|---|---|
| [Name] | Decider | At minimum: Mon AM, Wed AM, Fri PM. Ideally all 5. |
| [Name] | Facilitator | All 5 days |
| [Name] | [Design lead] | All 5 days (Tuesday and Thursday are sketch + prototype critical) |
| [Name] | [Engineering lead] | All 5 days (Thursday prototype-build critical) |
| [Name] | [PM / Researcher] | All 5 days (Friday interviews critical) |
| [Name] | [Customer expert / domain SME] | Mon (Map and Target), Fri (interview observation) |

[If cameo experts are recommended (additional domain SMEs, customer-success reps, legal, etc.), list separately with the specific session they should attend.]

## Decider Checkpoint

**Decider sign-off required before [scheduling Monday / activating customer recruiting / closing this diagnostic].**

- [ ] Decider confirms the verdict and accepts the diagnosis.
- [ ] Decider commits to attending the load-bearing windows (Mon AM, Wed AM, Fri PM) at minimum (if verdict is Go or Conditional Go).
- [ ] Decider acknowledges the documented preconditions and owns ensuring they are met before Monday (if Conditional Go).
- [ ] Decider authorizes the customer recruiting plan, including honorarium budget (if verdict is Go).
- [ ] Decider agrees the output should be a Friday scorecard plus a Decider review by 17:30 Friday with an explicit build / iterate / pivot / stop call.
- [ ] Decider acknowledges that the sprint will produce a single direction validated or invalidated; the prototype is not the product, and the team will not over-invest in the prototype as if it were.

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