Engineering Enablement by DX

DORA’s 2025 research on the impact of AI

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Relying solely on DORA's four key metrics is not sufficient to gauge AI impact in software delivery.
  • Understanding the five DORA metrics provides a broader understanding of software delivery performance.
  • AI acts as an amplifier, magnifying both successful processes and existing dysfunctions in engineering organizations.
  • Continuous dialogue with teams is essential to identify pain points that AI may be exacerbating.
  • Implementing an AI capabilities model can help organizations leverage AI effectively while addressing operational challenges.

Summary

The Insufficiency of Traditional Metrics

Nathan Harvey and Laura Tacho kick off the discussion by addressing the limitations of relying solely on the four key DORA metrics for measuring AI impact. They highlight that while these metrics provide a basic perspective on software delivery performance, they are only leading indicators and insufficient for deeper insights. Metrics alone cannot account for the complexities of software delivery, and there are additional factors in play that leaders need to consider for a comprehensive view.

The Evolving DORA Metrics

The conversation progresses to the evolution of DORA metrics, noting that for the past two years, research has expanded to include five software delivery performance metrics instead of just four. Leaders are advised to look beyond just these metrics and consider organizational health indicators, which will help them assess the real impact of their AI strategy.

AI as an Amplifier

AI is described as an amplifier that can highlight both strengths and weaknesses within engineering systems. If a team has efficient delivery processes, AI can significantly enhance productivity. Conversely, if dysfunction exists, AI will amplify these bottlenecks and issues instead of resolving them. Understanding how this amplification works is crucial for leaders managing AI integrations.

Analyzing AI Usage Patterns

The discussion touches on the differing patterns of AI usage between junior and senior engineers. A significant finding is that junior engineers tend to engage more actively with AI tools, leading to more code generation. However, this trend places greater pressure on the code review process, necessitating an analysis of team dynamics and the operational pressures that come with increased AI-induced workloads.

Developing an AI Capabilities Model

Nathan shares insights on the DORA AI capabilities model, which includes characteristics essential for maximizing AI benefits in software development. These characteristics, such as having a clear AI stance, healthy data ecosystems, and strong version control, help teams utilize AI effectively while minimizing friction. The model emphasizes that successful AI integration is contingent upon how organizations use these technologies.

The Importance of Open Communication

Towards the end, both Nathan and Laura stress the importance of open communication channels within teams. Direct conversations about friction points and challenges faced by teams can provide leaders with invaluable insights into operational bottlenecks, ensuring that AI is utilized in ways that reduce friction and enhance productivity.

Sponsors

  • DORA · State of AI-assisted Software Development 2025 report
  • DX · AI-assisted engineering: Q4 impact report

Show notes

Nathen Harvey leads research at DORA, focused on how teams measure and improve software delivery. In today’s episode of Engineering Enablement, Nathen sits down with host Laura Tacho to explore how AI is changing the way teams think about productivity, quality, and performance.


Together, they examine findings from the 2025 DORA research on AI-assisted software development and DX’s Q4 AI Impact report, comparing where the data aligns and where important gaps emerge. They discuss why relying on traditional delivery metrics can give leaders a false sense of confidence and why AI acts as an amplifier, accelerating healthy systems while intensifying existing friction and failure.

The conversation focuses on how AI is reshaping engineering systems themselves. Rather than treating AI as a standalone tool, they explore how it changes workflows, feedback loops, team dynamics, and organizational decision-making, and why leaders need better system-level visibility to understand its real impact.


Where to find Nathen Harvey:

• LinkedIn: https://www.linkedin.com/in/nathen


Where to find Laura Tacho: 

• LinkedIn: https://www.linkedin.com/in/lauratacho/

• X: https://x.com/rhein_wein

• Website: https://lauratacho.com/

• Laura’s course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-course


In this episode, we cover:

(00:00) Intro

(00:55) Why the four key DORA metrics aren’t enough to measure AI impact

(03:44) The shift from four to five DORA metrics and why leaders need more than dashboards

(06:20) The one-sentence takeaway from the 2025 DORA report

(07:38) How AI amplifies both strengths and bottlenecks inside engineering systems

(08:58) What DX data reveals about how junior and senior engineers use AI differently

(10:33) The DORA AI Capabilities Model and why AI success depends on how it’s used

(18:24) How a clear and communicated AI stance improves adoption and reduces friction

(23:02) Why talking to your teams still matters 


Referenced:
• DORA | State of AI-assisted Software Development 2025
• Steve Fenton - Octonaut | LinkedIn
• AI-assisted engineering: Q4 impact report

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file