Council Post: Why AI-Assisted Development Could Be The Next Productivity Shift

Jul 30, 2026 · 3 min read

Jess Turner, Executive Vice President, Global Head of Open Finance & Developer Experience at Mastercard.

The term “vibe coding” may be a buzzword, but it masks a far more consequential shift in how software is built. For large global organizations, especially those in regulated industries like financial services, where trust, security and reliability are nonnegotiable, new development approaches are often adopted deliberately. Change is not driven by hype; it must demonstrate proven outcomes under real-world constraints.

In my experience, software development has always evolved through cycles of skepticism followed by step-change gains. Early programmers worked with punch cards, often waiting hours or days for results. When interactive terminals introduced real-time feedback and iteration, critics worried discipline and quality would erode. Instead, productivity accelerated, and modern software engineering took shape.

AI-assisted development represents a similar inflection point. What began as code completion has rapidly evolved into systems that can interpret intent, reason through problems and adapt in real time. In controlled environments, AI agents can already generate applications, troubleshoot integration issues, identify the right technical resources and continue execution with limited intervention, producing functional software in minutes rather than weeks.

This is no longer confined to experimentation. Across engineering teams, I've seen AI-assisted development accelerating the creation of internal tools, testing frameworks, dashboards and production-grade components. Equally important, organizations are learning where these tools drive the most value and where human judgment remains indispensable. That early experimentation is critical. It builds confidence, shapes operating models and lowers the barrier to scaled adoption.

But speed alone is not the objective. When software can be created and modified at an unprecedented pace, the surrounding controls become even more important. Automation, security scanning, standards validation, performance testing and continuous quality assurance are no longer peripheral; they are foundational. AI does not diminish the need for engineering discipline; it heightens it.

Scaling this responsibly requires a shift in how organizations think about both development and governance:

1. AI-assisted development is a structural productivity shift. Like prior advances, AI-assisted development meaningfully expands how quickly and broadly teams can build, but its impact comes from sustained application, not isolated use cases.

2. The biggest gains come from coordination, not just code generation. AI excels at navigating dependencies, resolving integration challenges and streamlining repetitive workflows that slow teams down.

3. Enterprise adoption depends on trust. As development accelerates, the importance of security, validation and reliability only increases. These controls must be embedded into internal processes from the very beginning, not layered on later.

4. Human judgment remains central. AI can act and adapt, but intent, accountability and approval processes must stay with people, particularly in high-stakes environments.

5. Long-term advantage comes from pairing speed with governance. Organizations need to treat AI not as a tool but as an operating capability, one that is accelerated but rigorously controlled.

The shift underway is not about replacing developers or lowering standards. It is about re-architecting how software is built, combining machine-driven speed with human-led oversight. For enterprises, the challenge is not whether to adopt AI-assisted development but rather how to do so in a way that preserves trust while unlocking its full potential.

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