DORA metrics are still a useful foundation for measuring software delivery in 2026, but they don't capture the full impact of AI. They can’t tell you whether AI caused a change in the numbers, what that change cost, or whether the code will last. Keep DORA, add SPACE-style developer experience signals, and add an AI layer that separates AI-assisted work from human work and tracks cost per durable outcome.
If you’re asking… | Short answer |
|---|---|
Are DORA metrics still the right engineering productivity metrics in 2026? | Yes, as the base layer for delivery health. On their own they can’t attribute results to AI or show cost. |
Which tools measure AI impact on engineering output? | Tools that separate AI-assisted from human-written code and connect it to delivery and spend. Larridin does this across major coding assistants. |
What’s missing from DORA for AI teams? | AI attribution, cost, developer experience, and durability of code over longer windows. |
DORA or SPACE? | Both. DORA measures the delivery system; SPACE measures the experience and flow of the people inside it. |
DORA metrics measure how quickly and reliably a team delivers software using throughput and instability measures that any team can compute.
DORA’s current guidance covers five measures:
The 2025 DORA research based on nearly 5,000 technology professionals found AI adoption at 90% and described AI as an amplifier: it magnifies a team’s existing strengths and its existing weaknesses. The research also linked AI adoption to higher delivery throughput, reversing the prior year’s finding, while instability remained a concern.
DORA metrics describe what the delivery system produced, so they can’t explain why it changed or what it cost.
The gaps that matter most once AI is in the loop:
DORA is still useful, but it should be treated as the first layer of a larger measurement stack.
For a closer look at the output side, see how Larridin measures engineering work delivered.
SPACE adds the human side of productivity: satisfaction and well-being, performance, activity, communication and collaboration, and efficiency and flow.
The SPACE framework was published by Nicole Forsgren and colleagues in 2021, and matters more in AI-assisted teams because the work itself has changed. Engineers spend more time reviewing and steering AI output. Review load, interruptions, and trust in AI-generated code all affect delivery, and none of them show up in a deployment count. DORA’s 2025 research also flagged uneven trust in AI among developers, which is a SPACE-style signal worth tracking directly. An AI-native engineering playbook can help teams adapt their review and testing practices.
An AI-era stack has four layers: delivery, developer experience, AI impact, and cost.
Layer | Example metrics | Question it answers |
|---|---|---|
Delivery (DORA) | Lead time, deployment frequency, recovery time, change fail rate, deployment rework rate | Is the delivery system healthy? |
Developer experience (SPACE) | Satisfaction, flow time, review load, trust in AI output | Is the pace sustainable? |
AI impact | Share of AI-assisted code, durability of AI code, complexity-adjusted output | Is AI the reason results changed? |
Cost | Cost per durable outcome by team and tool | Is the improvement worth what it costs? |
Use developer productivity benchmarks to compare results before and after AI adoption.
Larridin covers the AI impact and cost layers. It attributes code to AI-assisted or human activity, scores PR complexity instead of counting PRs, and tracks cost per durable outcome across Cursor, Claude Code, GitHub Copilot, Codex, and Gemini Code Assist. The 5 Pillars of AI-Native Developer Productivity lay out the full model.
What you’re dealing with | What you need | How Larridin helps |
|---|---|---|
DORA improved, nobody knows if AI caused it | AI-assisted versus human attribution | Separates AI-generated code from human work |
Deployment frequency inflated by tiny PRs | Output weighted by difficulty | Complexity-adjusted output scoring |
Faster delivery, rising AI bill | Cost tied to delivery | Cost per durable outcome by tool and team |
Review queues growing | Visibility into where work waits | Engineering Intelligence on how engineers and agents work together |
No. Keep them as your delivery baseline. Without DORA you lose comparability over time and with the wider industry.
Indirectly, yes. More small AI-generated changes can raise deployment frequency without adding value, which is why complexity-adjusted output belongs beside it.
Weekly for team leads, monthly for engineering leadership, and quarterly in summary for the executive team.
Usually not; many tools compute DORA from your CI/CD data. You need an AI-aware layer to attribute results to AI and connect them to spend.