PreviewYou're previewing CTO AI Forge. Sign in to use it.Sign in
← All lessons
L2 · Measuring engineering impact8 min read

DORA metrics in the AI era

DORA (DevOps Research and Assessment, now part of Google Cloud) has studied software delivery for over a decade. Its four classic delivery metrics are the most widely used language for engineering performance:

  • Change lead time: from code committed to code running in production.
  • Deployment frequency: how often you deploy to production.
  • Change failure rate: the share of deployments that cause a failure needing remediation.
  • Failed deployment recovery time: how long it takes to recover from a failed deployment.

The first two measure throughput, the last two stability. DORA's research has found that the two go together: good teams are fast and stable.

The 2024 performance clusters

Each year DORA groups survey responses into clusters. In 2024:

LevelLead timeDeploy frequencyChange failure rateRecoveryShare
Elite< 1 dayOn demand (multiple per day)5%< 1 hour19%
High1 day – 1 weekDaily – weekly20%< 1 day22%
Medium1 week – 1 monthWeekly – monthly10%< 1 day35%
Low1 – 6 monthsMonthly – every 6 months40%1 week – 1 month25%

Notice the medium cluster's failure rate is lower than the high cluster's: DORA itself says improving matters more than reaching a label, and "the best teams are those that achieve elite improvement, not necessarily elite performance."

Why DORA matters more with AI

AI changes the input (more code, faster). DORA metrics measure the output of the system. If AI adoption rises while lead time stays flat and change-failure rate rises, AI is not helping delivery yet — DORA's own 2024 data found exactly this risk at the aggregate level.

Practical tips

  • Use the definitions consistently; document how your tools compute them.
  • Compare a team with itself over time, not teams with each other.
  • Add AI-specific context (adoption, AI-authored share) next to DORA, not instead of it.

What this means for the CTO

Make DORA's four metrics the backbone of your AI impact story: they are well understood, hard to game in combination, and they measure delivery rather than activity.

Report them per team and period alongside AI adoption. Your board-level message should read like: "AI adoption reached X%; lead time moved from A to B; change-failure rate stayed within our target." The productivity scorecard tool shows these bands for your own numbers.

Agree the definitions with your engineering leaders once — what counts as a deploy, a failure, the start of lead time — and keep them stable, so trends mean something.

Real example

In DORA's 2024 report, the elite cluster (19% of respondents) had change lead time under one day, on-demand deployments, a 5% change failure rate and recovery under one hour; the low cluster (25%) had lead times of one to six months and a 40% change failure rate. DORA notes the clusters emerge from the survey data each year rather than being set in advance (page 13). Source: DORA — 2024 Accelerate State of DevOps report (PDF) ↗

Use it

Quick check · 3 questions

  1. 1.Which two DORA metrics measure stability?

  2. 2.In DORA 2024, which slower-delivering cluster still had a lower change failure rate than the high cluster?

  3. 3.AI adoption rises, lead time is flat and change-failure rate rises. What does this suggest?

0 of 3 answered

Sources

Last reviewed 2026-10-01.