<!-- Stage-gate criteria · from Chapter 30 of The Product 360 Handbook -->

# Stage-gate criteria · [Gate name] · [Product or portfolio]

**Gate type:** New segment / General availability / Price change / R1 Consider retirement / R2 Announce end-of-sale / R3 End support / R4 Decommission
**Gatekeepers:** [names and roles]   **Decision owner:** [name]

## Deliverables the team brings
1.
2.
3.

## Must-meet criteria (any "No" stops the gate)
| Criterion | Yes / No | Evidence |
|---|---|---|
| Strategic fit with the agreed strategy | | |
| Legal and contract review complete | | |
| Security and privacy review complete | | |
| No unmitigated customer harm (data loss, broken integrations, compliance gaps) | | |
| Funded owner for the next stage | | |

## Should-meet criteria (score 1 to 5)
| Criterion | Weight | Score | Evidence |
|---|---|---|---|
| Customer evidence | | | |
| Market attractiveness | | | |
| Competitive advantage | | | |
| Feasibility or migration readiness | | | |
| Financial return or savings | | | |
| Risk (lower risk scores higher) | | | |
| **Weighted total** | | | |

## Decision rules (agreed before the gate)
- Go if all must-meet criteria pass and the weighted total is at least [threshold].
- Recycle if [condition]. Hold if [condition]. Kill if [condition].

## Outcome
Decision: Go / Kill / Hold / Recycle. Approved plan and resources: [summary]. Next gate date: [date]. Recorded in the decision log on [date].
