<!-- Pivot-or-persevere review · from Chapter 21 of The Product 360 Handbook -->

# Pivot-or-persevere review · [Bet] · [Date]

**Cadence:** every [6 to 8] weeks or once per cycle   **Decider:** [Name]
**Attendees:** product trio, Decider, finance partner, [others]

## Evidence summary
- Dashboard link and milestone status:
- Experiments since last review, with learning cards:
- What moved, and why we think so:
- What didn't move:

## Warning signs
- Are we solving an important problem? Evidence:
- Are early adopters actually adopting? Evidence:
- Does the product deliver what it promises? Evidence:
- Is the team chronically frustrated, with only modest gains from tuning?

## Options
| Option | Pivot type (if any) | What we keep | What changes | Cost | Evidence for |
|---|---|---|---|---|---|
| Persevere | n/a | | | | |
| Pivot | zoom-in / zoom-out / customer segment / customer need / platform / business architecture / value capture / engine of growth / channel / technology | | | | |
| Stop | n/a | | | | |

## Decision
- Decision:
- Rationale (one paragraph):
- What we keep from the past (validated learning carried forward):
- New or revised hypothesis:
- Next milestone and review date:
- Who will be told, and how: