<!-- Process health check · from Chapter 11 of The Product 360 Handbook -->

# Process health check · [Team] · [Quarter] · [Date]

Score each from 1 (poor) to 5 (strong) with evidence. Pick at most two to improve next quarter.

| # | Dimension | Score | Evidence |
|---|---|---|---|
| 1 | Goals are outcomes, not output | | |
| 2 | WIP stays within limits | | |
| 3 | Cycle time trend is stable or improving | | |
| 4 | Few items age past the SLE | | |
| 5 | Changes are small (batch size) | | |
| 6 | Review and verification wait time is short | | |
| 7 | Escaped defects and incidents are low | | |
| 8 | Discovery kills or reshapes ideas before build | | |
| 9 | PM and team have regular direct customer contact | | |
| 10 | Agent-generated changes have a low revert rate | | |
| 11 | The team reports a sustainable pace | | |
| 12 | Every ceremony produces a decision or a change | | |

## Two changes for next quarter
1. [Change], owner, how we'll know it worked:
2.

## Method still fits?
Has the work changed (share unplanned, complexity, commitments, team count)? Yes / No. If yes, rerun the selection guide.
