The CIO Role Just Split in Two. Here’s What You Need to Know.

# ai# cioleadership# enterprisestrategy# technologyleadership
The CIO Role Just Split in Two. Here’s What You Need to Know.Nick Talwar

Why the Best AI Leaders Run Offense and Defense Simultaneously Fourteen AI initiatives on a single...

Why the Best AI Leaders Run Offense and Defense Simultaneously

Fourteen AI initiatives on a single roadmap, governed by one steering committee, measured against one set of success criteria. Half are automating existing workflows to protect margins. The other half are building capabilities the company has never offered before. Meanwhile, the budget, risk framework, and quarterly check-in schedule remain stagnant.

This is what most enterprise AI portfolios look like right now. And it explains why so many of them feel stuck.

The two halves of that portfolio are fundamentally different games. One is about protecting what already works. The other is about building what comes next. Each requires different ownership, different timelines, different metrics, and different tolerance for ambiguity. Running them as a single strategy is like training for a marathon and a sprint on the same schedule. The structure guarantees that one of them suffers.

What Most Organizations Miss

McKinsey’s Global Tech Agenda 2026 found that the CIOs delivering measurable value have made a specific shift. They’ve moved technology from a cost center to what McKinsey calls a “value creator,” embedding AI and data directly into operating models.

But the research surfaced a clear divide between organizations that are simply modernizing their technology estate and those that are rewiring for competitive advantage.

That divide maps to a pattern I keep running into with enterprise leaders. The companies actually moving forward are playing two distinct games at once:

  1. With defense, they’re using AI and Agents to protect the core business. Automating manual workflows, tightening operational efficiency, reducing cost structures that have been bloated for years.

  2. On offense, they’re building new capabilities. New products, new revenue streams, new ways of reaching customers that weren’t possible eighteen months ago.

Most organizations don’t have a mental model for this split. They’re either in pure cost-cutting mode or chasing growth, and the AI and Agentic AI strategy simply reflects whichever game the board happens to be pressuring this quarter.

What Defense Actually Looks Like

Defensive AI and Agent targets processes you understand well, with outcomes you can measure in months and risk profiles you can model. Automated claims processing. Intelligent document extraction. Predictive maintenance on equipment that’s already generating revenue.

The success criteria are clear. Faster cycle times, lower error rates, reduced headcount for routine tasks, better margins on existing lines of business. The value case is arithmetic, and the ROI conversation is relatively straightforward.

What Offense Actually Looks Like

Offensive AI builds capabilities that didn’t exist before. You’re not optimizing a known process. You’re testing whether a new process should exist at all.

These projects look like using AI to enter adjacent markets with personalized products, or building recommendation engines that fundamentally change how customers discover what you sell, or creating internal decision-support tools that give your operators information advantages competitors don’t have.

The success criteria are murkier. You’re measuring learning velocity, market signal, and option value. The ROI conversation is harder, and the organizational patience required is significantly higher.

When Efficiency Eats Innovation

When companies run offense and defense under the same governance structure, the defensive projects almost always win the resource fight.

Defense gets measured on efficiency, cost reduction, and operational reliability. The governance is tighter and accountability sits with operational leaders who own the processes being improved.

Offense gets measured on learning rate, market validation, and strategic optionality. The governance is much lighter, and the timelines are longer.

Overall, defensive projects are easier to justify, easier to measure, and easier to get approved. So offensive projects get deprioritized because they can’t compete on the same ROI framework.

The result is a portfolio that looks busy, but only plays one game. The company gets more efficient at what it already does while falling behind on what it could become. The board sees cost savings and assumes the AI and Agent strategy is working, but nobody’s building anything that changes the company’s competitive position.

The Diagnostic

If you’re running AI and Agent initiatives right now, here’s a quick test. Look at your active portfolio and sort every project into one of two columns. Column one: protecting existing revenue and margin. Column two: building something you’ve never had before.

If you can’t sort them cleanly, your strategy is probably conflated.

The companies losing ground on AI and Agents aren’t necessarily the ones spending too little. They’re the ones who never made the split visible, never assigned ownership to each side, and ended up with a portfolio that defaults to whichever pressure is loudest.

Making the split explicit is the first step toward making it work.

Nick Talwar is a CTO, ex-Microsoft, and a hands-on AI engineer who supports executives in navigating AI adoption. He shares insights on AI-first strategies to drive bottom-line impact.

Follow him on LinkedIn to catch his latest thoughts.

Subscribe to his free Substack for in-depth articles delivered straight to your inbox.

Watch the live session to see how leaders in highly regulated industries leverage AI to cut manual work and drive ROI.