Decision
Convert MVP evidence into iterate, pivot, pause, or scale decisions.
Key takeaways
- The sprint ends with a decision, not a shipped build: choose iterate, pivot, pause, or scale.
- Scale only when the test shows strong repeatable demand and delivery is feasible; pause when evidence is weak and no near-term learning path exists.
- Review evidence against five questions: did the target customer show up, understand the promise, reach value, commit, and can you deliver?
- Capture the outcome in a decision memo that records the result, evidence, decision, and next experiment.
The sprint is not complete when the build ships. It is complete when the team makes a decision.
Decision Options
| Decision | When to choose |
|---|---|
| Iterate | Signal is positive but a clear bottleneck remains |
| Pivot | The problem or segment is wrong, but adjacent signal exists |
| Pause | Evidence is weak and no near-term learning path is obvious |
| Scale | The test shows strong repeatable demand and delivery is feasible |
Evidence Review
| Question | Evidence |
|---|---|
| Did the target customer show up? | Segment/source data |
| Did they understand the promise? | CTA, demo, reply, objection data |
| Did they reach value? | Activation or concierge outcome |
| Did they commit? | Money, time, contract, repeated usage |
| Can we deliver? | Support load, manual effort, quality issues |
Decision Memo
# MVP Decision Memo
## Hypothesis
...
## Result
...
## Evidence
- Quantitative:
- Qualitative:
## Decision
Iterate / Pivot / Pause / Scale
## Next Experiment
...