100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
DevOps

Lead Time for Changes

DORA delivery performance metric

IntermediateConcept3.2K learners

Lead time for changes is a DORA metric measuring the time it takes for a code commit to be deployed successfully to production.

Definition

Lead time for changes is a DORA metric measuring the time it takes for a code commit to be deployed successfully to production.

Overview

Lead time for changes captures the full journey of a code change from the moment a developer commits it to the moment it is running safely in production. It differs from broader concepts like "time to market," which might include product discovery and design, by focusing narrowly on the engineering pipeline: code review, automated testing, build, and deployment. DORA's research identifies lead time as one of the four key metrics that distinguish elite-performing software organizations. Elite teams typically move a change from commit to production in under an hour, while low performers can take months. Short lead times indicate a healthy, low-friction delivery pipeline — fast code review, reliable automated tests, minimal manual approval gates, and deployment tooling that can ship a validated change without lengthy staging cycles. Reducing lead time usually means addressing multiple parts of the pipeline at once: breaking large pull requests into smaller ones for faster review, investing in test suites that are both fast and trustworthy, moving from manual QA gates to automated quality gates, and adopting practices like trunk-based development that avoid long-lived branches. Feature flags also help by letting code merge to the main branch and deploy continuously even when the feature itself is not yet ready for users. Like other DORA metrics, lead time for changes is most useful as a trend indicator over time rather than a single point-in-time number, and it is typically viewed alongside deployment frequency, change failure rate, and mean time to recovery to get a balanced picture of delivery performance.

Key Concepts

  • Measures time from code commit to successful production deployment
  • One of the four core DORA metrics
  • Elite teams achieve lead times under one hour
  • Reflects pipeline health: review speed, test reliability, deployment automation
  • Improved by smaller pull requests and trunk-based development
  • Distinct from broader product lead time or time to market
  • Best tracked as a trend rather than a single snapshot

Use Cases

Diagnosing bottlenecks in code review or CI pipeline stages
Justifying adoption of trunk-based development or feature flags
Comparing engineering velocity across teams or quarters
Setting SLAs for how quickly hotfixes can reach production
Informing investment decisions in test automation infrastructure

Frequently Asked Questions

From the Blog