Strategy Table.
WS07 turns the Gate-A-approved option into strategy slices — coherent deliverable chunks, sequenced around outcomes rather than deliverables. Each slice delivers something worth having on its own and sets up the next one.
Purpose
A big-bang delivery plan is a commitment to discover reality all at once. Slicing the approved option produces interim releases — each of which can be validated, adjusted, or descoped without tearing up the rest of the program. The sequencing rationale explains why slice N precedes slice N+1.
Template
| Slice name | Short label (e.g., "Pilot with one site", "Integration layer", "Reporting enhancements") |
|---|---|
| Outcome | What the slice delivers that's valuable on its own |
| Rationale for order | Why this slice comes before the next one |
| T-shirt size | S / M / L / XL — rough effort |
| Dependencies | External dependencies that must be in place |
| Acceptance signal | What proves the slice shipped successfully |
Outcome-first sequencing
Sequence slices by value realization, not by technical convenience. "Build the database layer first because it's foundational" is an anti-pattern — it produces no user-visible outcome until slice N+1 lands. Prefer sequencing where each slice advances WS04 Business Objective measurably.