1 min lesson
Close the loop back to the pain
Use two rows in "Close the loop back to the pain" to state the practical decision rules.
Step 1 of 2
Close the loop back to the pain
A POC that proves "the tool is nice" doesn't close. A POC that proves it moved the exact number from discovery does. At the readout, you're connecting two dots you set up weeks earlier.
- Discovery said
- 40 devs losing ~3 hrs/week to toil
- POC proved
- Cohort reclaimed ~2.6 hrs/dev/week
- Therefore
- ~104 hrs/week back, roughly 2.5 engineers of capacity
- Discovery said
- New-hire ramp takes 6 weeks
- POC proved
- Trial hire productive in ~4 weeks
- Therefore
- Faster ramp on every future hire
- Discovery said
- Velocity flat into a Q3 launch
- POC proved
- Cohort PR cycle time down ~20%
- Therefore
- Launch risk lowered, so the compelling event is addressed
| Discovery said | POC proved | Therefore |
|---|---|---|
| 40 devs losing ~3 hrs/week to toil | Cohort reclaimed ~2.6 hrs/dev/week | ~104 hrs/week back, roughly 2.5 engineers of capacity |
| New-hire ramp takes 6 weeks | Trial hire productive in ~4 weeks | Faster ramp on every future hire |
| Velocity flat into a Q3 launch | Cohort PR cycle time down ~20% | Launch risk lowered, so the compelling event is addressed |
Example numbers, not benchmarks. The readout proves the quantified pain from week one actually moved.