Another Chief to the Bonfire

AI doesn’t demand a new breed of leader, it demands a new breed of organization. Until we redesign the underlying architecture, no amount of chiefs will save us.

Last week, MIT Sloan Management Review published “Why AI Demands a New Breed of Leaders” by Faisal Hoque, Thomas H. Davenport, and Erik Nelson. It’s a piece that perfectly captures everything wrong with how organizations approach transformation. They correctly identify that 91% of leaders cite cultural barriers as the main obstacle to AI adoption, then propose... wait for it... adding another C-suite role.

This is like discovering your house is on fire and deciding what you really need is a Chief Fire Management Officer.

What MIT Sloan Thinks Is Happening

The article paints a familiar picture: AI is creating unprecedented challenges. Organizations need leaders who can navigate ethics, foster culture change, manage human-AI collaboration. Traditional CIOs are too busy with operations. HR hasn’t stepped up. Therefore, we need a new hybrid role, the Chief Innovation and Transformation Officer, to bridge these gaps.

It’s a seductive narrative. It’s also completely wrong.

What’s Actually Happening

This isn’t a leadership problem. It’s an architecture problem. Let me show you why.

Strip away the consultant-speak and here’s what the article actually documents:

Organizations discovering their fundamental architecture is broken:

• Systems designed for control, not adaptation

• Leadership structures that reinforce silos rather than dissolve them

• Optimization for internal efficiency over human value

• “Transformation” efforts that just rearrange broken foundations

The Zillow and Air Canada examples they cite? Perfect illustrations of what happens when you layer AI onto systems never designed for human flourishing. You don’t get innovation. You get algorithmic extraction at scale.

Zillow lost $300 million not because they lacked a transformation officer, but because they tried to turn homes (the most human of spaces) into algorithmic commodities. Air Canada’s chatbot didn’t fail because of missing leadership. It failed because they automated away human judgment in moments requiring deep empathy.

“AI won’t break your organization. It will reveal that it was already broken.”

And California State University? They had a “clear strategic vision” and even assembled an AI Workforce Acceleration Board with 10 leading AI companies. Within a week, the whole thing imploded. Why? They forgot that universities are communities of humans, not deployment zones for corporate AI strategies. No amount of C-suite leadership could have saved a plan that fundamentally misunderstood its own organization.

The C-Suite Graveyard

Here’s the delicious irony: These organizations already have CIOs, CTOs, CDOs, and enough acronyms to fill an alphabet soup. Now they want to add a CITO (Chief Innovation and Transformation Officer) to fix what all those other chiefs couldn’t?

This isn’t transformation. It’s organizational hoarding.

Look at the track record:

• Chief Digital Officers have one of the highest churn rates in the C-suite, average tenure under 3 years

• Chief Innovation Officers rarely produce lasting innovation; most become corporate theater managers

• Chief Transformation Officers typically vanish after 18-24 months once the “transformation” inevitably stalls

• Chief Data Officers often struggle to get basic data governance implemented, let alone drive insights

Every new C-suite role is an admission of failure. A monument to the dysfunction you’re unwilling to address. “We need someone to work across silos” means you’ve accepted silos as permanent. “We need someone to drive transformation” means you’ve built an organization that resists its own evolution.

It’s like hiring a Director of Unclogging instead of fixing the pipes.

And what magical powers will this CITO possess? According to the article, they’ll “navigate complex ethical landscapes,” “foster cultural transformation,” and “manage human-AI collaboration.” In other words, they’ll be responsible for everything the existing leadership can’t or won’t do.

“A new chief is not a strategy. It’s a confession.”

Even more telling is how they use “AI persona management” to justify another role, adding more complexity. Thoughtful AI personas do matter. Someone has to decide how these systems speak, what they prioritize, and whose values they encode. But that is core product, design, and governance work, not a reason to invent a new throne in the corner office. When you turn persona management into a special role, you don’t elevate the work; you centralize what should be a distributed, accountable practice.

The Questions They’re Afraid to Ask

Instead of “What new role do we need?” try these:

Why do our systems require heroic leadership to function? If you need a transformation superhero, you’ve designed a system that fights against its own success.

What constraints are we preserving by adding complexity? Every new role adds coordination overhead, decision layers, and political dynamics. You’re feeding the disease.

How might we design organizations that transform naturally? What if adaptation wasn’t a special project but your default state?

The Bandwagon of Delusion

PepsiCo, Standard Chartered, JPMorgan Chase. The article parades these companies as success stories for hiring transformation chiefs. But what are they really celebrating? That these billion-dollar organizations need a special executive to do what startups do naturally: adapt.

It’s like applauding someone for hiring a breathing coach. If you need one, the problem runs deeper than technique.

The Un-Design Alternative

Real transformation doesn’t come from adding chiefs. It comes from dismantling the constraints that make transformation necessary in the first place.

Look at organizations that actually adapt without heroic leadership:

• Haier replaced hierarchy with 4,000 self-managed microenterprises, no transformation officer needed

• Buurtzorg disrupted Dutch healthcare with self-organizing teams of nurses, no innovation chief required

• Spotify uses autonomous tribes and squads, adaptation is built into the architecture

• Amazon’s two-pizza teams make decisions at the edge, innovation happens everywhere, not in a corner office

Notice the pattern? These organizations don’t need transformation officers because transformation is their default state.

What Un-Design Actually Means

Un-Design means:

• Removing the constraints that make transformation necessary

• Dissolving silos, not working around them

• Designing architectures that adapt continuously

• Shifting from command-and-control to distributed intelligence

• Replacing “hero leaders” with self-healing systems

• Creating structures that serve human intent, not organizational control

Instead of a CITO, try:

• Dissolving the silos that require cross-functional heroes

• Distributing innovation authority throughout the organization

• Designing systems that evolve continuously, not through “initiatives”

• Creating structures that serve human intent, not organizational control

The companies succeeding with AI aren’t the ones with the best transformation officers. They’re the ones who’ve made transformation officers obsolete.

The Architecture of Delusion

That “91% cite cultural challenges” statistic? It’s not a hiring problem. It’s an architecture problem.

You can’t solve cultural dysfunction by adding another executive any more than you can cure diabetes by hiring a Chief Sugar Management Officer. The solution isn’t managing the symptoms better. It’s addressing the systemic disease.

And where’s HR in all this? The article admits they “have, for the most part, not stepped up.” Of course they haven’t. HR is too busy managing the human casualties of systems designed for extraction, not flourishing. They’re the EMTs at the bottom of the cliff, not the architects who might question why we keep pushing people off it.

Organizations keep hoping for a messiah in a C-suite when what they need is a mirror. The problem isn’t that you lack the right leader for AI transformation. The problem is you’ve built an organization that requires transformation at all.

What Leaders Should Actually Do

• Architect adaptive systems, not heroic roles. Build structures that evolve without intervention

• Redesign governance to reduce dependency on centralized authority. Push decisions to the edge

• Shift innovation rights to teams closest to user value. Let those who understand the problem own the solution

• Build human-centered data models that reflect intent, not bureaucracy. Design for what people are trying to achieve

• Make transformation continuous, not episodic. Evolution should be your default state

• Measure adaptability, not adherence. Success is how quickly you respond to change, not how well you follow the plan

This isn’t about better leadership. It’s about making leadership less necessary.

The Two Paths

The choice is yours: keep adding complexity or start removing constraints.

A Different Path Forward

What if we stopped adding complexity to manage complexity?

What if change was your default state, not a special project?

What if innovation wasn’t the exception but the rule?

The future belongs to organizations with the courage to Un-Design, to systematically dismantle what makes adaptation heroic instead of natural.

Stop adding chiefs. Start removing the kingdom.

Transformation doesn’t fail because you’re missing another leader. It fails because the organization was designed for control, not adaptation.

If you want true transformation, don’t ask who should lead it. Ask why you needed it in the first place.