Shared metric visibility
When multiple teams chase one metric, this template keeps baseline → target → date honest. Fill in your metric table or Browse the runbooks index. Pair it with the Monthly Release Rhythm so status stays current at each tag.
Template
| Metric | Baseline | Target | Target date | Status band | Notes / owner |
|---|---|---|---|---|---|
| Weekly onboarding NPS | 38 | ≥50 | Next quarterly checkpoint | 🟡 | Product Ops — blocked on support scripts |
| Docs release cadence | 1/mo | 1/mo (no skips) | Rolling monthly | 🟢 | Docs Steward — on track |
| Interrupt resolution <10 min | 62% | 80% | Next Fast Support update | 🟠 | Support Lead — need new Fast Support flow |
Color legend: 🟢 on track, 🟡 at risk, 🟠 behind.
How to use it
- Duplicate the table into the shared status doc.
- Keep baselines immutable; adjust targets only during planning.
- Update status bands weekly and drop a link to the latest receipt (release, PR, metric screenshot).
Related references
- Transition operating promises — Promise owners should include their metric deltas in status updates.
- State ledger — Confirm the metrics show up in the generated entry each time you tag a release.
- Fast support index — Add a metric row if interrupts are part of the promise you’re tracking.