Skip to content
black full logo-May-16-2026-10-06-02-7734-PM

CIO Scrutiny Is Up. Agility Is Down. Something Has to Give.

CIOs are getting hammered.

Years of being responsible, and accountable, for security, governance, data infrastructure, a budget, and so much more - now being 180 pivoted in the name of generative AI. It's as though all the requirements of yesterday are being thrown into the wind even if only for AI novelty.

Having 900 agents that all define "revenue" differently isn't going to create better companies, it's going to ruin great companies. 900 broken agents isn't something to brag about. The whole AI approach in enterprise is frankly unacceptable.

  • Using agents in copilot to "make this email better". Works great.
  • "Read this deck". Works great.
  • "Do [this] when [that]". Ok, rules based is cheaper but sure.
  • "Tell me about my lifetime customer value." Crossed the line - now you're working with structured data, ambiguity, multiple secure system fragmentation, governance, and so much more.

 

Your options for the last bullet:

  1. Let anyone create any agent in copilot and give them access to connect the data they need to answer the question. Operational outcome: everyone using a different formula, people with different access to different systems using different fields for the variables, having an LLM do math (excess cost and inconsistent responses), loading data into an LLM (security breach). Business outcome: the company becomes even less efficient than it was before.
  2. Let a model pull from a data warehouse where the data has already been processed. Ok, you've created continuity and you're consistent in the management of your data. You're handling things as you did prior to gen AI which is secure, precise and consistent. Ok, so same process as before but now in natural language - so you've added cost to an approach that was mastered before with BI and added zero value and you have a layer between your intelligence and your execution systems (physical tech or software) meaning you'll never automate with write functions. This is what the data warehouses want you to not notice: they're vintage.
  3. Embrace a full federated infrastructure that enables intelligence into all systems so your entire data estate can be orchestrated with precision, security, and consistency. Take your systems that are required to define LTV the way your company defines it consistently and centralize that intelligence so all models, agents, users are securely held automatically to that standard. Get rid of the data warehouse that's suffocating you and embrace AI completely while putting resources against developing functions instead of being bogged down in data management. The question ultimately comes down to: do you want to spend your time preparing to work by embracing vintage systems or get to the work with modern infrastructure that enables you in the age of AI?

 

Adding layers is exhausting, it's expensive, and it's degrading the talent of teams to function at their potential.

The usual response to slowness is to add another layer. A faster pipeline. A reverse sync. A real-time copy sitting on top of the batch copy. It buys a little speed and adds one more thing to govern and pay for. You can't fix the problem of data warehouses when it's their feature and not their bug: it's a data copying problem that adds more data copying.

Federation inverts the whole thing. You don't move the data. You connect to it where it lives and read it in real time. No warehouse in the middle. No pipeline breaking at 2am. No third vendor whose only role is translating between the first two.

Look at what that does to the CIO's three demands. The vendor list shrinks, because the middle layer is gone. Governance gets tighter, because the data never leaves the systems that already secure it. Answers come back in hours instead of a quarter, because nothing has to round-trip to a copy. The demands that were pulling against each other start pointing the same direction.

I don't think this pressure is a phase. Governance expectations are climbing and they won't reverse. Budgets are getting harder to defend, not easier. The teams that win the next few years won't be the ones who squeeze a little more performance out of the warehouse. They'll be the ones who stop maintaining an architecture built for a slower decade.

So I'll leave data leaders with one question. If you stripped your stack down to only the parts that actually answer questions, how much would be left?

For most companies the honest number is small. That's not a tooling gap you can buy your way out of. It's the architecture telling you it can't carry what's coming.