DORA Metrics: Vital Signs for Your CI/CD Pipeline
DORA metrics are four vital signs for your software delivery process, balancing speed and stability. They benchmark DevOps performance from commit to production. The main footgun is optimizing for speed while ignoring stability, leading to frequent outages.
Why it exists
Before the DORA metrics, 'engineering performance' was hard to quantify and often relied on vanity metrics like lines of code. Teams struggled to prove that DevOps practices were working or to identify which process changes actually improved delivery without causing instability.
The mental model
Think of DORA metrics as the vital signs for your software delivery process. Two metrics measure your speed and throughput (Deployment Frequency, Lead Time for Changes), while two measure your stability and resilience (Change Failure Rate, Time to Restore Service). They provide a balanced, outcome-oriented view of system health, not individual output.
How it works
The four metrics are collected from version control and CI/CD systems. First, Deployment Frequency tracks how often you successfully release to production. Second, Lead Time for Changes measures the time from a commit to it running in production. Third, Change Failure Rate is the percentage of deployments that cause a production failure. Fourth, Time to Restore Service is how long it takes to recover from a production failure.
When to use it
Use DORA metrics to establish a baseline for your team's performance and track improvements over time. They are excellent for justifying investments in tooling, automation, or process changes. They help shift conversations from 'are we busy?' to 'are we delivering value effectively and reliably?'.
When not to use it
Never use DORA metrics for individual performance reviews. This incentivizes gaming the system (e.g., making tiny, frequent commits to boost deployment numbers) and destroys psychological safety. They are system-level metrics, not a scorecard for individual engineers. Also, avoid comparing your absolute numbers to 'elite' performers without context; focus on your own team's trend of improvement.
One canonical example
A platform team notices their Lead Time for Changes is high, taking weeks. Digging in, they find that manual QA and staging environment contention are the bottlenecks. They invest in better automated testing and on-demand preview environments. Over the next quarter, they see Lead Time decrease to days and Deployment Frequency increase, all without a rise in the Change Failure Rate. The metrics prove their investment paid off.
Interview question
Which scenario represents an inappropriate application of DORA metrics?
- a.Comparing a team's current performance against its historical trends to show improvement.
- b.Quantifying the effectiveness of new automation tools implemented in the CI/CD pipeline.
- c.Evaluating an individual developer's contribution to deployment frequency for performance reviews.Correct
- d.Identifying bottlenecks in the software delivery process by analyzing lead time for changes.
Why? this is the answer
The card explicitly states, "Never use DORA metrics for individual performance reviews." Using them for individual evaluation incentivizes gaming the system and undermines psychological safety, as they are intended as system-level metrics. The other options describe valid uses for DORA metrics, such as tracking team improvements, justifying investments, and identifying process bottlenecks.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on devops — each one lists the topics its interview covers.
See open roles