Speed is here. Control is not.

AI tools are making teams faster across the board. Code is being written at scale, pipelines are being built in hours and automation is spreading into areas that once required significant manual effort. On the surface, this looks like progress.

But a more complicated picture is emerging underneath. According to Google's "2024 DORA report," increased AI use speeds up code reviews and documentation but comes with a 7.2% decrease in delivery stability. Independent code analysis found that AI-generated pull requests show roughly 1.7 times more issues than human-only ones, and at least 48% of AI-generated code contains security vulnerabilities. Systems are more connected, which means when something breaks, it tends to break across more layers at once.

Two global firms we worked with tell the same story: Development velocity climbed, and within months, production issues followed. In both cases, the bottleneck was not the development team. Quality had simply not kept pace with the tools driving it forward.

Speed without control is not transformation. It is an accumulation of risk.

Quality engineering has to grow with AI, not just keep pace with it.

Most teams have already moved quality into the sprint. Shift-left is no longer a differentiator; it is the baseline. But in an AI-driven environment, that is not enough on its own.

The challenge now is not where quality sits in the process. It is whether quality engineering is maturing at the same rate as the AI capabilities being built around it. The recent "World Quality Report" found that while nearly 43% of organizations are now actively pursuing GenAI in their quality engineering practices, only 15% have achieved enterprise-scale deployment. That gap between experimentation and genuine maturity is where most of the risk lives.

Validating systems that evolve continuously, governing AI outputs for reliability and maintaining data integrity across increasingly connected platforms all require a fundamentally different level of capability and ownership than in-sprint testing alone can provide. The firms pulling ahead are not just embedding quality earlier. They are scaling the quality function itself, in depth and sophistication, alongside every AI capability they add.​

The engineer gap is the real leading indicator.

The same shift playing out at the organizational level is already visible at the individual level. Fifty-one percent of professional developers now report using AI tools daily, saving an average of 3.6 hours per week. The engineers who have made these tools part of how they actually work, rather than waiting for structured training programs, are operating at a materially higher level than those still working the way they did two years ago.

That gap is widening. And it matters because organizations tend to adjust slowly. Structures, processes and habits take time to change. Engineers growing alongside these tools will not wait for that adjustment. As the capability gap widens within teams, maintaining consistent quality across the work being produced becomes increasingly difficult. The productivity divergence between AI-native engineers and those who have not yet adapted is becoming one of the clearest leading indicators of where quality risks will surface next.​

What will the next generation of firms look like?

The companies that come out strongest will not simply be faster versions of what exists today. Quality, engineering, data and AI will function as one integrated system rather than departments passing work between each other. Teams will be smaller but significantly more capable. Leaders will not just be managing activity; they will be driving outcomes directly, with commercial models increasingly tied to results rather than inputs.

McKinsey estimates that generative AI could add between $2.6 and $4.4 trillion annually across use cases, but capturing that value requires more than adoption. It requires the organizational maturity to govern what is being built. The common thread among the firms getting this right is that they treated quality engineering as a core strength early, not an afterthought once the problems surfaced.

​AI will set the pace of change. Quality engineering will determine who can sustain it. The firms that move early will carry a meaningful advantage, and when this transition fully plays out, the distance between them and those who wait will be very hard to close.​

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?