AI transformation is a systems problem: a conversation with Justin Reock, DX | Augment Code<br>Skip to content
ProductCosmosCLIChangelog
SolutionsCode ReviewReview every PR with agentsTest CoverageCoverage that climbs, suites that stay greenIncident ManagementInvestigate alerts before humans arriveTicket to PRAssign a ticket, merge a reviewed PRLarge ProjectsFrom design doc to shipped featureAutomationsRecurring work as repeatable workflowsSecurity RemediationFrom CVE alert to a reviewed fixMigrationsModernization as a program, not a projectOnboardingRamp every engineer in daysTeam Standards at ScaleYour best workflow, everyone's default
Context EnginePricingDocsBlogResourcesWorkflowsCustomersCareersStatus PageTrust CenterSecurity
svg]:px-3 flex-1" href="/contact">Talk to Salessvg]:px-3 flex-1" href="https://cosmos.augmentcode.com">Sign in
svg]:px-2.5 group rounded-full px-4" href="/contact">Book demo
Back to Blog<br>Every engineering leader I talk to is trying to transform. They want their teams to be AI-native. They're rolling out tools, tracking adoption, watching dashboards. But the harder questions are the ones most leaders aren't asking out loud. What are we actually trying to change? What does success look like? How should we be thinking about this?<br>Justin Reock, CTO at DX, spends his days talking to engineering leaders about exactly these questions. DX sits on top of telemetry and survey data from hundreds of thousands of engineers across hundreds of companies, including a longitudinal study of 500 companies tracking PR velocity from November 2024 through February 2025. I sat down with him for the latest episode of We Built What. The data tells a clear story: AI is exposing a systems problem that was always there. The companies winning right now are the ones who see it.
The data says calm down. It also says you've been looking at the wrong thing.<br>Here's the headline number from DX's study: a 7.5% median uplift in PR velocity. The average was 13%. The top performer hit 70%.<br>"Who wouldn't invest in the 10 or 15 percent uplift in overall productivity?" Justin asked. "I think we just need to start allowing ourselves the grace that 10 or 15 percent is actually successful."<br>That's a recalibration most leaders need to hear, but it's not the most important thing the data is telling us.<br>Atlassian's State of DevEx research has consistently shown that engineers only spend about 16% of their time actually writing code . Justin made the implication clear: "Even if you had a tool that was 100% accurate, required no rewrite, no refactor or review, and was instantaneous, you're still only attacking 16% of the problem."<br>If you point AI at that 16% and leave the other 84% untouched, single-digit productivity gains are exactly what you should expect.<br>The systems lesson is older than DevEx<br>This isn't a new finding. The coding war games of the 1970s found something that has held up for fifty years. Across different organizations, top performers produced at 11 times the rate of the bottom performers. Within the same organization, the spread between individuals was only about 20%.<br>W. Edwards Deming, decades before that, articulated it even more cleanly: 90 to 95% of an organization's productivity output is determined by the system, not the worker.<br>Google has rediscovered the same thing more recently. When they studied 180 teams to figure out what made the best ones work, the composition of the team didn't matter. The norms did. The same individual could thrive on one team and struggle on another. The strongest predictor of performance is the system, the manager, and the team they're embedded in.<br>AI doesn't change this. It amplifies it. Drop a powerful AI tool into a system designed for slow, sequential, gate-heavy work, and you'll get a marginal improvement on a fundamentally constrained pipeline. Drop the same tool into a system designed for flow (modular code, fresh docs, fast CI, psychological safety to experiment) and you get the 70% uplift.<br>What "the system" actually means<br>Justin laid out what the highest-performing companies in DX's data have in common:<br>[ Coming up next ]
The New Code Review Workflow for AI-Native Engineering Teams<br>See how leading teams keep code review fast and rigorous as AI writes more of the code.
svg]:px-4 group" href="https://watch.getcontrast.io/register/augment-code-the-new-code-review-workflow-for-ai-native-engineering-teams?utm_source=blog&utm_medium=content_cta&utm_campaign=webinar&utm_content=ai-transformation-is-a-systems-problem">Save your seat— Thu, Jul 9 // 9:45 AM PDT
Code modularity and accessible, current documentation. Stale docs and tangled code aren't just engineer pain points. They're inference inputs.<br>Fast CI/CD pipelines. If your build takes 40 minutes, your agent's feedback loop takes 40 minutes too.<br>Education and time to absorb it. DX's data showed something counterintuitive. Light AI adoption actually decreases productivity. Only moderate-to-heavy adoption outperforms...