The CIO’s new job description: Chief transformation officer

I’ve been in this industry for 32 years. I’ve watched the CIO role evolve from “keep the servers running” to “align IT with business strategy” to “drive digital transformation.” Each of those transitions took roughly a decade to complete.

This one is happening in months.

The arrival of enterprise AI has compressed the CIO evolution timeline in ways none of us expected. Two years ago, most CIOs I talked to were managing cloud migrations and modernizing legacy systems. Important work, but familiar work. Today, those same CIOs are fielding calls from every business unit leader in the company, all asking some version of the same question: “What’s our AI strategy?”

And here’s the thing nobody tells you about that moment: The question isn’t really about AI. It’s about whether the CIO can lead the most significant operational change the enterprise has faced since the internet.

The shift that changed everything

For years, the “CIO as strategic business leader” narrative was aspirational. Conference keynotes talked about it. Consulting firms published frameworks for it. But in practice, most CIOs were still spending 70% of their time keeping the lights on and 30% on strategic initiatives, if they were lucky.

AI flipped that ratio overnight. Not because CIOs suddenly got more strategic. Because the business suddenly needed them to be.

When your CEO reads about a competitor deploying AI agents that cut customer service response times by 40%, the first call isn’t to McKinsey. It’s to you. When your CFO wants to understand how AI could change the cost structure of the business, they’re not Googling it. They’re walking down the hall to your office.

The CIO went from requesting a seat at the strategy table to being the person everyone else at the table is looking at for answers.

But here’s what makes this particular moment different from previous technology shifts: The speed. Cloud migration was a decade-long journey. Digital transformation was a multi-year initiative. AI is moving on a timeline measured in quarters. The large language models that organizations are building strategies around today didn’t exist in their current form two years ago. The agentic AI frameworks that are reshaping how we think about automation are months old, not years. CIOs are being asked to make enterprise-scale bets on technology that is evolving faster than any planning cycle can accommodate.

That requires a fundamentally different kind of leadership. Not the kind that produces a three-year roadmap and executes against it. The kind that can make smart bets under uncertainty, course-correct quickly and bring the organization along for the ride.

Why most AI strategies fail (and what CIOs can do about it)

Here’s a number that should keep every IT leader up at night: Industry research consistently suggests that AI projects fail at a rate higher than other IT projects. I’ve started calling this “pilot purgatory,” and I see it everywhere. Last June, Gartner predicted that 40% of Agentic projects will be cancelled by 2027.

The pattern is painfully predictable. A business unit gets excited about a use case. IT spins up a proof of concept. The demo looks great. Everyone celebrates. And then the project stalls because nobody planned for data quality, integration complexity, security requirements, change management or the dozen other things that separate a demo from a production system.

This is where the CIO’s role becomes critical, and it has nothing to do with picking the right model or the right vendor.

The CIOs who are succeeding at AI transformation share a common approach. They treat it as an enterprise capability problem, not a technology problem. That means thinking about three things simultaneously:

First, the data foundation. AI is only as good as the data it can access. I talk to organizations every week that want to build sophisticated AI applications on top of fragmented, siloed, inconsistent data. It doesn’t work. The unsexy truth is that data architecture, data quality and data governance are the preconditions for everything else. There’s no shortcut that bypasses this reality.

Second, the organizational model. Who owns AI in the enterprise? Is it centralized in IT? Federated across business units? Some hybrid? Every model has trade-offs, and CIOs who don’t make a deliberate choice end up with chaos by default. Shadow AI projects proliferate. Security gaps emerge. Redundant vendor contracts stack up. The CIO has to architect the organizational structure for AI adoption with the same rigor they’d apply to a technology architecture.

Third, the cultural transformation. This is the hardest part, and it’s the part that most technology leaders are least comfortable with. AI adoption is fundamentally a change management challenge. You can deploy the most sophisticated AI platform in the world, but if your workforce doesn’t trust it, doesn’t understand it or doesn’t know how to work alongside it, you’ve built an expensive shelf decoration.

The cultural change nobody wants to talk about

Let me spend a moment on that third point because I think it’s where CIOs have the greatest opportunity to differentiate.

I’ve seen a lot of technology adoption cycles. The pattern is always the same: The technology arrives faster than the organization’s ability to absorb it. We saw it with PCs, with the internet, with cloud, with mobile. And mobile had the additional feature that people had access to it in their personal lives before their work lives.

AI is that pattern on steroids, including the personal life angle.

The difference this time is that AI doesn’t just change what tools people use. It changes what their jobs are. When a customer service agent goes from answering questions to supervising an AI that answers questions, that’s not a tool change. That’s an identity change. When a developer goes from writing code to reviewing and directing AI-generated code, the fundamental nature of the work shifts.

CIOs who understand this are approaching AI adoption differently. They’re investing as much in training and change management as they are in technology. They’re creating safe spaces for experimentation where failure is expected and encouraged. They’re being transparent about what AI will and won’t change about people’s roles.

Most importantly, they’re leading with empathy. The workforce anxiety around AI is real and legitimate. Dismissing it with platitudes about “AI won’t replace you, a person using AI will replace you” isn’t leadership. Understanding the specific fears of specific teams and addressing them honestly is leadership.

I think about my parents here. My dad was a football coach and typing teacher. My mom ran a community college computer lab. Both of them spent their careers helping people learn new skills during periods of technological change. The typing teacher who saw adding machines leave and word processors arrive didn’t panic. He adapted what he taught and helped his students adapt, too. That’s the CIO’s job right now: Be the person who helps the enterprise learn how to work differently, not just the person who deploys new tools.

From pilot to production: The execution gap

The cultural challenge is real, but it’s not the only gap. There’s an execution gap that’s equally dangerous, and it lives in the space between “we proved the concept” and “this runs reliably at enterprise scale.”

I see CIOs struggle with this because the incentive structures work against them. Pilots are cheap, fast and produce exciting demos. Production deployments require investment in monitoring, security, data pipelines, integration and ongoing maintenance. The board wants to see innovation. The CISO wants to see guardrails. The business units want results yesterday. The CIO has to balance all three while building something that actually works.

The CIOs getting this right are the ones who refuse to greenlight a pilot without a clear path to production. Before the first line of code gets written, they’re asking: What data does this need? Where does that data live? Who owns it? What are the security and compliance requirements? How will we measure success? What happens when the model is wrong?

Those aren’t exciting questions. They’re not the questions that make headlines. But they’re the questions that separate the 5% of AI projects that make it to production from the 95% that don’t.

What this means going forward

The CIO role isn’t just evolving. It’s being fundamentally rewritten.

The CIOs who will define the next era of enterprise technology aren’t the ones with the deepest technical expertise, though that still matters. They’re the ones who can translate between the boardroom and the engineering floor. The ones who can build a business case for AI investment that speaks in outcomes, not features. The ones who can lead cultural change at scale while simultaneously managing the most complex technology stack in enterprise history.

That’s a tall order. But here’s what more than three decades in this industry has taught me: the CIOs who thrive in moments like this aren’t the ones who have all the answers. They’re the ones who are honest about what they don’t know, surround themselves with people who complement their gaps and move forward anyway.

The business isn’t waiting for a perfect AI strategy. It’s waiting for a CIO who’s willing to lead through the uncertainty.

And that’s always been the real job.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?