Skip to main content

Change lead 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.

Arithmetic mean commit-to-first-successful-production-deployment duration; also publish median/p90 and sample count.

ContractDefinition
NumeratorSum of elapsed hours from committed_at to first successful production deployment for each service+commit
DenominatorCount of eligible service+commit pairs with valid mappings
ExpressionN / D
Aggregationmean
Unithours/change
Eligible populationChanges first successfully deployed to a service in reporting window; rollout retries collapse to same logical deployment.
ExclusionsNonproduction, duplicates, no-op deployment with no new commits; missing mappings shown as coverage loss.
Events and sourcechange.committed; deployment.completed; VCS immutable commit timestamps and release manifest
Owner / cadencePlatform & IT / Weekly per service
Missing evidenceMissing commit mapping or negative/skewed duration excluded from numeric sample, reported explicitly; no zero substitution.
Gaming and limitsTimestamp rewriting and cherry-picking fast work; lock change mapping and show undeployed backlog age. Descriptive signal, not causal AI productivity attribution. Source completeness, task mix and sampling limit inference; report uncertainty. Not PR cycle time, effort saved, or a complete view of unfinished changes. p90 uses nearest-rank sorted sample.

Read the shared collection and safeguards before collecting data; see the synthetic example and limits.

Return to Skills Measurement.