Engineering Enablement by DX

The current impact of AI on engineering velocity: What 400 companies are seeing (Abi Noda & Brian Houck)

· Summarized

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

Key takeaways

  • Most organizations see modest improvements (around 10-15%) in engineering throughput from AI, far below the industry hype of 10x gains.
  • Coding constitutes only about 14% of developers' work; thus, AI tools targeting coding alone have limited impact on overall productivity.
  • Unrealized productivity gains may be diverted to review, quality assurance, or lost to wait times, which explains the gap between expected and actual improvements.
  • Rapid velocity might introduce risks like technical debt, reduced quality, and cultural resistance—collectively termed 'false velocity'—which can undermine long-term business value.
  • Leaders should expand their focus beyond code to optimize the entire SDLC, including workflows, documentation, and autonomous agents.
  • Measuring the effectiveness of AI tools requires new frameworks that evaluate both human and agent productivity, including the human costs like cognitive debt.
  • Adopting AI responsibly involves addressing human factors, ensuring long-term understanding and mastery over AI-driven systems.

Summary

Introduction and Context of DX's Research on AI in Engineering

This section introduces the podcast's setting at the DX Annual event, with host Justin Riyak welcoming guests Abi Noda and Brian Houck. Abi Noda shares the motivation behind DX's recent research into AI’s impact on engineering velocity, driven by the gap between industry hype and real-world observations. DX’s study aims to understand what organizations are actually experiencing as they scale AI adoption, especially after observing modest gains in throughput during the past year.

Research Methodology and Participant Selection

Abi Noda details how DX approached the study, selecting companies with mature AI adoption—defined as over 75% of developers actively using AI tools—and with more than 100 engineers. They excluded companies affected by M&A or IPO events to avoid regulatory confounders. The research emphasizes longitudinal data analysis at the organizational level to better understand causality, as opposed to cross-sectional analysis, to gauge the true impact of AI on engineering throughput over time.

Findings on AI's Impact on Engineering Throughput

The research reveals that AI adoption has led to a modest increase in throughput—typically around 8-11%, or roughly 10-15%, far lower than the often-promised 10x gains. This discrepancy is attributed to various factors, including the realization that coding is only about 14% of developers' work, along with new bottlenecks introduced by automation, cultural resistance, and friction in adoption. The findings challenge the hype of dramatic productivity boosts and highlight the complexity of measuring true value.

Understanding the Limits and Nuances of Productivity Gains

The discussion covers why AI productivity gains tend to be lower than expectations. Follow-up interviews with developers suggest that much of their time isn't spent coding, which diminishes the impact of AI tools focused solely on code. Developers are often using saved time for reviewing, managing technical debt, or waiting, which impacts overall productivity metrics. Abi emphasizes that these nuanced realities explain the modest gains observed.

Unintended Consequences and Risks of Accelerated Development

The podcast explores potential downside effects of increased velocity, such as quality degradation, rising costs, and the concept of 'false velocity'—where teams appear faster but fail to deliver real business value. Cultural challenges, like prioritizing speed over meaningful innovation, are discussed as crucial considerations for engineering leaders to avoid unintended long-term risks like technical and cognitive debt.

Beyond Coding: Broader Focus Areas for AI Adoption

Guests recommend that organizations look beyond just improving coding efficiency. They suggest improving the entire Software Development Life Cycle (SDLC), enhancing developer experience, and exploring autonomous engineering ideas. Emphasis is placed on applying AI to optimizing workflows, documentation, and creating more autonomous agents that augment human work in parallel, rather than replacing it.

Human Factors and Cognitive Debt in AI-Driven Engineering

The conversation emphasizes the human costs of AI adoption, including cognitive debt—the mental load and understanding gaps in complex systems. Influenced by Margaret Ann Storrey’s research, the discussion considers how AI can lead to a loss of human mastery over systems and the importance of measuring and managing these human factors to sustain long-term quality and innovation.

Evolving Measurement Frameworks for AI Impact

Abi Noda discusses how DX is updating its measurement frameworks to better evaluate both human and agent productivity. New metrics include tracking AI agent effectiveness and user feedback, as well as distinguishing between acceleration of human effort versus augmentation through autonomous agents. This approach aims to provide a clearer picture of real productivity and ROI in AI-enhanced engineering.

Sponsors

  • DX · Recorded live at DX Annual, Abi Noda, co-founder and CEO of DX, joins Brian Houck of Microsoft to share an early look at DX’s new research on AI’s impact on engineering velocity.

Show notes

Recorded live at DX Annual, Abi Noda, co-founder and CEO of DX, joins Brian Houck of Microsoft to share an early look at DX’s new research on AI’s impact on engineering velocity.

Drawing on data from a sample of DX customers, they discuss what companies are actually seeing as AI adoption matures. Most organizations in the study saw pull request throughput increase by 10 to 15 percent—far more modest than the 10x gains often promised in industry headlines.

They explore why coding remains only a small part of developer work, where time saved by AI may be going, and the unintended consequences of moving faster, from shifting bottlenecks to “false velocity.” Abi also shares how engineering leaders are applying AI beyond coding and how DX is evolving its measurement framework to account for both human and agent productivity.


Where to find Brian Houck: 

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


Where to find Abi Noda:
• LinkedIn: https://www.linkedin.com/in/abinoda


In this episode, we cover:

(00:00) Intro

(00:53) What motivated DX’s research into AI’s impact on engineering velocity

(02:36) How DX designed the study and selected companies

(04:54) What DX’s data reveals about AI’s impact on engineering throughput

(06:31) Why PR throughput was the most practical metric to publish

(08:21) Why AI productivity gains are lower than many leaders expected

(10:24) How an all-in culture can amplify AI productivity gains

(12:35) Why it’s hard to track where AI-generated time savings are going

(15:04) Unintended consequences of AI-driven productivity gains

(17:12) Why leaders should look beyond coding to the rest of the SDLC

(19:43) Cognitive debt and the human costs of AI-assisted development

(21:33) How DX’s AI measurement framework is evolving

(24:42) How to make agents more effective


Referenced:

• DX Core 4 Productivity Framework 

• DORA, SPACE, and DevEx: Which framework should you use?

• Time Warp: The Gap Between Developers’ Ideal vs Actual Workweeks in an AI-Driven Era - Microsoft • Research

• How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt

• Measuring AI code assistants and agents

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