This standard ensures teams minimise lead time—from the start of work to safe production deployment—by targeting Lead Time for Change (LTFC), a key DORA metric. Shorter lead time lowers risk, accelerates learning, and increases delivery flow efficiency.
Aligned to our "Fast Feedback Loops" and "Limit Work in Progress (WIP)" policies, this standard reveals and resolves bottlenecks that slow value creation. Without it, teams endure lengthy development cycles, delayed feedback, and hidden coordination costs.
| Category | Description |
|---|---|
| People & Culture | Teams are unaware of lead time or do not view it as critical. Work is picked up without clarity on flow or feedback. |
| Process & Governance | No visibility into delivery flow or delay causes. Lead time varies significantly. |
| Technology & Tools | No tooling exists to measure lead time. Work status changes are not captured. |
| Measurement & Metrics | Lead time is not measured, understood, or discussed. |
| Category | Description |
|---|---|
| People & Culture | Teams begin to discuss flow efficiency and delays. Lead time is approximated manually or via ticket dates. |
| Process & Governance | Delivery stages are loosely defined. Some efforts to scope work for smaller batch sizes emerge. |
| Technology & Tools | Basic workflow tracking exists (e.g. ticket status, CI logs). Measurement depends on manual updates. |
| Measurement & Metrics | Lead time is captured inconsistently across teams. |
| Category | Description |
|---|---|
| People & Culture | Teams value fast, testable delivery and reduce WIP proactively. Engineers inspect delays during retros. |
| Process & Governance | Delivery flow is standardised and supported by lightweight governance. Lead time is visible across teams. |
| Technology & Tools | Lead time is measured using automation across SCM, CI/CD, and workflow systems. Consistent instrumentation is adopted. |
| Measurement & Metrics | Lead time is tracked by phase (e.g. dev, review, test, deploy). Trends are reviewed and used to inform decisions. |
| Category | Description |
|---|---|
| People & Culture | Teams actively use flow metrics to drive improvements. Flow health is reviewed during planning and reviews. |
| Process & Governance | Governance is adaptive and responsive to bottlenecks. Flow acceleration efforts are supported by leadership. |
| Technology & Tools | Tools capture time-in-status, deploy duration, and review lag. Dashboards support value stream mapping. |
| Measurement & Metrics | Lead time thresholds are monitored and improvements are tracked. Metrics are used to target systemic change. |
| Category | Description |
|---|---|
| People & Culture | Teams run experiments to reduce lead time and share learnings. Fast feedback is part of delivery culture. |
| Process & Governance | Flow metrics inform product roadmap, team shape, and WIP policies. Improvements scale across domains. |
| Technology & Tools | Real-time telemetry drives alerts on flow inefficiencies. Data feeds into platform and tooling strategies. |
| Measurement & Metrics | LTFC is continuously improving across teams. Flow performance is integrated into engineering health metrics. |