How to Misuse & Abuse DORA Metrics

In this enlightening paper, Bryan Finster explores the unintended consequences that can arise from misusing the four key DORA metrics that many organizations rely on to measure software delivery performance. While these metrics—deployment frequency, lead time, change fail percentage, and mean time to restore (MTTR)—were instrumental in the research that established the effectiveness of DevOps practices, Finster argues they are often misapplied as standalone improvement targets.

The paper dives into real-world examples of how an excessive focus on these metrics in isolation can drive the wrong behaviors, like deploying code hastily at the expense of quality. Finster stresses the DORA metrics must be balanced with other measures of effectiveness, sustainability, flow, and culture. Metrics are most effective as indicators of progress when used by teams to improve their own unique process and outcomes rather than for comparing teams to each other.

Finster provides practical tips for using metrics responsibly to nurture a culture of continuous learning and improvement. He emphasizes the importance of educating the entire organization on what the metrics really mean, providing actionable feedback to teams, and avoiding the pitfalls of measuring individuals. When used appropriately, DORA metrics can be part of a holistic approach to enhancing software delivery capabilities. But as Finster concludes, there are no simple metrics—measuring any human activity is complex and requires thoughtful experimentation and adaptation.