Failed deployment recovery time
Target operating model — recommended contracts, not installed collection. All owner and cadence entries below are proposals to confirm before the pilot, not assigned responsibilities or approved schedules.
Unimplemented metric — no live telemetry. This is a prospective contract, not an implemented calculation or collector.
Mean elapsed time from production deployment failure onset to service restoration, with median/p90 and unresolved count/age.
| Contract | Definition |
|---|---|
| Numerator | Sum of recovery_at minus failure_started_at in hours for recovered eligible deployment failures |
| Denominator | Count of recovered eligible deployment failures with valid timestamps |
| Expression | N / D |
| Aggregation | mean |
| Unit | hours/failure |
| Eligible population | Production deployment failures beginning in window; latest verified restoration if a recovery is rescinded. |
| Exclusions | Nondeployment incidents; invalid timestamp pairs reported missing, not treated as instantaneous recovery. |
| Events and source | deployment.failed; service.restored; incident service |
| Owner / cadence | Platform & IT / Weekly with unresolved failures |
| Missing evidence | Unresolved failures reported separately and excluded only from recovered-duration distribution; prevent declaring improvement without their visibility. |
| Gaming and limits | Premature recovery declarations or omit hard cases; require operational readback and carry unresolved ages. Descriptive signal, not causal AI productivity attribution. Source completeness, task mix and sampling limit inference; report uncertainty. Not all-incident MTTR; recovered-only sample has survivorship bias. p90 nearest rank. |
Read the shared collection and safeguards before collecting data; see the synthetic example and limits.
Return to Skills Measurement.