DORA Four Keys — Deep Dive

DORA Four Keys: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Time to Restore. Elite: deploy on-demand, <1h MTTR, <15% CFR. Speed and stability are positively correlated — not a tradeoff.

Overview

Speed and stability, measured

The DORA (DevOps Research and Assessment) Four Keys are the industry-standard metrics for software delivery performance. They come from six years of research across 32,000+ professionals in the annual State of DevOps reports.

The four metrics

Deployment Frequency — How often code deploys to production
Lead Time for Changes — Commit to production
Change Failure Rate — Share of deployments causing a production failure
Time to Restore Service (MTTR) — How long it takes to recover from a failure

Performance bands

Deployment Frequency — Multiple times per day — Once per day to once per week — Once per week to once per month — Less than once per month
Lead Time for Changes — Under 1 hour — 1 day to 1 week — 1 week to 1 month — 1 to 6 months
Change Failure Rate — 0-15% — 0-15% — 16-30% — 16-30%
Time to Restore — Under 1 hour — Under 1 day — 1 day to 1 week — 1 week to 1 month

> [!NOTE] The bands shift between annual reports, so treat them as a guide rather than fixed thresholds.

Speed and stability move together

> [!IMPORTANT] Elite teams achieve high speed and high stability at the same time: the two are positively correlated, not a trade-off.

Key concepts

Deployment Frequency: How often a team releases to production. Best predictor of lead time — frequent deploys mean smaller batches, lower risk per deployment, faster feedback loops. Trunk-based development and feature flags enable high frequency.
Lead Time for Changes: Clock starts at commit; clock stops when live in production. Includes code review + CI build + deployment pipeline + manual approval gates. Reveals where time is spent between code-complete and delivery.
Change Failure Rate: Percentage of deployments causing a production incident. Measures deployment quality. Reduced by: comprehensive automated testing, canary deployments, feature flags for instant rollback.
Time to Restore (MTTR): Incident detection to full service recovery. Key enablers: good observability (fast detection), runbooks, feature flags, canary rollbacks, on-call engineers with authority to act.
Elite Profile: Deploy multiple times per day, <1h lead time, <15% CFR, <1h MTTR. Elite teams prove speed and stability are mutually reinforcing, not a tradeoff.

When to use it

Establishing a baseline before a DevOps transformation initiative
Tracking impact of CI/CD improvements over time
Identifying bottlenecks: high frequency + high CFR = test coverage gap; low frequency + low CFR = batch release risk aversion
Executive reporting on engineering effectiveness with industry benchmarks

Interview questions

What are the DORA Four Keys and elite benchmarks?
How do you measure Lead Time for Changes in practice?