AI adoption is done. The ROI isn’t. What DX’s Q2 2026 Report reveals in July 2026
Arthur Magne
With adoption above 90% across the industry, the question is dead. DX even admits it in the introduction of their new Q2 report: there is no control group left. You can’t compare AI teams to non-AI teams because non-AI teams almost no longer exist.
The real questions now sit on every CTO’s desk: are we actually gaining productivity? And is the ROI positive, given the money we’re pouring into tokens?
DX’s Q2 report is the most honest attempt I’ve seen at answering both. And the answers should make a lot of engineering leaders uncomfortable.
First, the data behind it
This isn’t a vibes-based survey. The report measures 500+ engineering organizations on the DX platform, from fewer than 50 to over 10,000 employees, across Europe, Asia and North America, and across industries including Finance, Retail and Healthcare. The reporting period covers April to June 2026, with trend data going back to Q3 2025.
It combines two complementary sources: system metrics pulled automatically from source control, CI/CD pipelines and AI tools, and survey metrics capturing what developers actually experience. Findings are organized around the DX Core 4 (Speed, Effectiveness, Quality, Impact) and their AI Measurement Framework (Utilization, Impact, Cost).
One caveat worth stating: the sample skews toward organizations mature enough to invest in productivity measurement. The real industry picture is probably worse.
Now, the findings.
PR inflation: speed is eating discipline
The report states that PR size nearly doubled over the year, a pattern it describes as “AI-driven inflation rather than disciplined, testable code.”
Read that again. Median PR size went from 42 to 72 lines of code in four quarters.
Press enter or click to view image in full size
This is exactly what we’ve been saying for more than ten years: trust and quality must come before speed. The AI race is so intense right now that teams are bypassing principles we spent a decade establishing. Small batches. Testable increments. Single-purpose changes. All of it is quietly eroding because the agent can generate a complete feature in one shot, so why bother slicing?
Here’s why you should bother. When humans developed features, we naturally cut them into small, deliverable pieces. That slicing gave us control and deep knowledge of what shipped. We could test and experiment on each increment. With AI, the first output is already “complete,” so people are tempted to enlarge what they ask for. The model over-delivers. Entropy grows. And confidence in the generated code drops, precisely because the PRs are bigger.
The data confirms the loop: incremental delivery is the single sharpest decline among all developer experience factors this quarter.
Maintainable code that nobody trusts
Press enter or click to view image in full size
DX State of AI Impact in Engineering: Q2 Report
The most fascinating tension in the report is this one: code maintainability improved by 3.8%, while change confidence fell by 6.1%. As DX puts it, these two metrics are “historically correlated, but are now in tension.”
AI helps engineers understand the code in front of them. But faith in what actually ships is slipping.
My reading: given the sheer volume of code now produced (52.7% of all code is AI-authored, up from 19% a year ago), humans simply can’t stay in the loop anymore. Reviewing every diff at generation speed is physically impossible. So the human becomes the bottleneck, and under pressure, the human exits the inner loop.
Press enter or click to view image in full size
This is not a bug of the transition. It’s the transition itself. It’s the same conclusion pushed by a growing number of voices in the industry: the developer’s place is no longer inside the inner loop, line by line. It’s on the outer loop. Defining intent, designing the verification system, owning the gates, carrying the responsibility for what ships. If you don’t build that outer loop deliberately, you get the worst of both worlds: humans who no longer read the code, and no system that reads it for them.
The slow teams are winning on quality
Here’s the counterintuitive finding leaders should sit with. Traditional industries and Financial Services, the slowest-moving segments on throughput, report the highest perceived software quality. Financial Services posts around 77 to 81% perceived quality with the lowest throughput of all verticals. Healthcare, this quarter’s throughput leader, sits at the lower end of the quality range.
Speed and perceived quality are not moving together. And leaders should stop assuming they will.
This confirms something important: the companies extracting the most from AI are not the ones generating the most code. Some organizations go slower but put governance and a proper harness in place to control the quality of what gets produced. The report itself notes that structured rollouts are positively associated with success in AI initiatives. Those teams will likely end up with the better return on investment, because they can actually trust and build on what they ship.
Velocity without a harness isn’t acceleration. The report says it bluntly: some teams are simply shipping defects faster.
Press enter or click to view image in full size
The big one: spend is outrunning the return
This is the point that has evolved the most in recent months, and the one that will dominate every budget conversation in the second half of 2026.
The numbers are brutal. Median quarterly AI spend grew from roughly $1.5K to $44K in a single year. In the Tech sector alone, that’s about a 28x increase. Per-developer spend jumped from $9 to $191 per month.
Press enter or click to view image in full size
DX State of AI Impact in Engineering: Q2 Report
And what did that buy? The innovation ratio, the share of engineering time spent creating new features versus maintenance, stayed essentially flat the entire year, moving from 57% to 58%.
Time savings are real and growing, now over 6 hours per week on average. But those saved hours are not visibly converting into new value creation at the portfolio level. They’re being absorbed by the same organizational friction AI was supposed to eliminate: reviews, approvals, CI wait times, meetings.
Even more uncomfortable for enterprise buyers: smaller organizations pay the highest price per seat and extract the most throughput per dollar. Bigger AI budgets don’t guarantee better returns, and may even come with diminishing ones.
Stop counting tokens. Start counting saved weeks.
The report nails the instinct problem: leaders reach for new metrics like token counts and lines of AI-generated code, but these metrics only show how work is changing, not whether outcomes are improving.
I’ve lived this, and it’s what I keep pushing to teams. The accounting is backwards.
Don’t look at a task and say “this cost me $300 in tokens, that’s expensive.” Flip it. Start from the value: this feature was mandatory to win market share, or to improve the stability of the product. Without AI, it would have taken me two weeks. With AI, it took three days.
Now, and this is the critical condition, if I have a solid system with a proper harness, and I can trust what was produced as if I had built it myself over those two weeks, then the math is simple. I saved eleven days of development. Eleven days I can now invest in other high-value work. Whatever I paid in tokens for that task, the ROI is massively positive.
That’s how you should calculate it. And that’s how you should present it to your leadership. Token spend without a value denominator is noise. Token spend divided by trusted, delivered outcomes is a business case.
Notice the load-bearing word in that reasoning: trust. Without the harness, without the gates, without the governance that lets you treat AI output as if it were your own two weeks of work, the eleven saved days are fiction. You’ll pay them back later, with interest, in debugging and rework.
Think in systems, not in PRs
Uma Namasivayam from Dropbox asks the right question in the report: if your code throughput tripled tomorrow, could your SDLC absorb it? Their early signs say no. In his words, “it breaks everywhere.”
Human review. Code review. CI pipelines. Testing. Production visibility. Every downstream gate is cracking under generation pressure.
Press enter or click to view image in full size
The real mistake is to focus on code generation and PR production instead of thinking about the complete system. If you 10x one link of the chain and leave the others untouched, you haven’t gained productivity. You’ve manufactured bottlenecks. It’s far better to incrementally improve every part of the system, generation, review, testing, deployment, observability, to raise total throughput, than to over-optimize one stage and starve the rest.
The report’s data backs this everywhere: deployment frequency is up double digits, but review turnaround, local iteration speed and ease of delivery all declined. The overall Developer Experience Index slipped from 67 to 65. Individual output surges, the system absorbs the slack.
What leaders should actually do
The report’s prescription aligns with everything we advocate. While deployment frequencies increased across most segments, change failure rates remain highly volatile, with outliers now reaching plus or minus 3 percentage points against a 4% industry benchmark. Some teams are shipping defects proportionally faster.
The answer is to scale your quality infrastructure to match code generation speed: AI-driven testing, standardized prompts, updated code review protocols. I’d add: explicit gates, shared engineering standards that agents can consume, and observability on what your agents actually do.
Pair every speed metric with a quality counterweight. Deploy frequency with change failure rate. Throughput with change confidence. Time savings with innovation ratio. If one side of the pair moves and the other doesn’t, you don’t have acceleration. You have a system in tension, and it will resolve itself at your expense.
The starting line, not the finish line
The organizations best positioned for the rest of 2026 are the ones treating AI adoption as the starting line, not the finish line.
Adoption is done. 90%+ of the industry is there. What separates teams now is everything around the model: the harness, the governance, the verification loops, the measurement frameworks that connect tokens to outcomes.
The bottleneck moved from writing code to trusting code. The teams that build for trust will collect the ROI everyone else is still trying to justify.
Based on the State of AI Impact in Engineering: Q2 Report by the DX Research Team, published July 2026, covering 500+ engineering organizations from April to June 2026.