The Four DORA Metrics Every Team Should Track

How do you know if your software delivery is actually improving? Years of research distilled the answer into four metrics — the DORA metrics — that together capture both speed and stability. Here is what each one means and how to move it.

1. Deployment frequency

How often you release to production. High-performing teams deploy frequently — often many times a day — in small, safe increments. If you deploy rarely, each release is big, risky and stressful. Smaller and more frequent is safer, counter-intuitive as that sounds.

2. Lead time for changes

How long it takes for a committed change to reach production. Short lead times mean fast feedback and responsiveness. Long lead times usually point to manual steps and bottlenecks in the path to production.

3. Change-failure rate

The percentage of deployments that cause a problem needing remediation. This is your stability check — it stops teams from gaming speed at the expense of quality.

4. Time to restore service

When something does break, how fast you recover. Failures are inevitable; what separates strong teams is how quickly they detect and fix them.

Speed and stability together

The key insight from DORA is that speed and stability are not a trade-off — the best teams score well on both. Automation is how you get there: CI/CD shortens lead time and increases frequency, while automated testing, observability and safe deployment strategies keep failure rates low and recovery fast.