# Foundation Sprint Readiness Assessment: [Initiative name]

<!-- One-line description of the initiative the team is considering running a Foundation Sprint for. -->

## Inputs Captured

**Initiative description:**

> [The project, product area, or strategic question, as the team named it.]

**Team composition draft:**

- [Name] ([role]; Decider candidate)
- [Name] ([role])
- [Name] ([role])
- [Name] ([role])

**Decider name and availability:** [Name; full-day availability for Day 1 and Day 2; or partial availability with details]

**Existing customer/market knowledge level (self-assessed):** [_/10. Brief note on basis for the score.]

**(Optional) Existing competitor and alternative knowledge:** [Notes on what is and is not known.]

**(Optional) Logistics constraints:** [Date windows, location, format.]

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

[One-sentence summary explaining the verdict.]

| Criterion | Status | Notes |
|---|---|---|
| 1. Initiative is named and concrete | [PASS / YELLOW / FAIL] | [Notes] |
| 2. Stakes are meaningful | [PASS / YELLOW / FAIL] | [Notes] |
| 3. Team has existing customer/market knowledge | [PASS / YELLOW / FAIL] | [Notes] |
| 4. Decider is available | [PASS / YELLOW / FAIL] | [Notes] |
| 5. Team size is appropriate (max 5) | [PASS / YELLOW / FAIL] | [Notes] |
| 6. Inputs are collected | [PASS / YELLOW / FAIL] | [Notes] |
| 7. Output has a path to testing | [PASS / YELLOW / FAIL] | [Notes] |
| 8. Organization tolerates explicit tradeoffs | [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.]

## 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.]

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

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

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

## Recommended Attendees (Go or Conditional Go only)

| Attendee | Role | Required for which sections |
|---|---|---|
| [Name] | Decider | All |
| [Name] | Facilitator | All |
| [Name] | [PM / Design / Engineering / Customer expert / etc.] | [Day 1 AM / Day 2 PM / all] |
| [Name] | [Role] | [Sections] |

[If cameo experts are recommended, list separately with the specific section they should attend.]

## Decider Checkpoint

**Decider sign-off required before [scheduling Day 1 / closing this diagnostic].**

- [ ] Decider confirms the verdict and accepts the diagnosis.
- [ ] Decider commits to attending both full days as Decider (if verdict is Go or Conditional Go).
- [ ] Decider acknowledges the documented preconditions and owns ensuring they are met before Day 1 (if Conditional Go).
- [ ] Decider agrees the output of the sprint should be a Founding Hypothesis ratifiable by end of Day 2 (if verdict is Go).
- [ ] Decider acknowledges that the sprint will force tradeoffs; one strategic direction becomes the top bet and others become backup or are dropped.

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