The standard advice in 2026 is that any serious enterprise needs an AI Transformation Office. A dedicated unit. A senior leader. Workstreams. Governance. A roadmap. Every major advisor is selling some version of this, every board paper recommends it, every Fortune 500 is staffing one. The case looks airtight.

It is the wrong answer. Not "imperfect." Wrong. The very act of creating an AI Transformation Office is the most reliable signal I have ever found that a company has already lost the transformation. I know that contradicts the room you were just in. I have been in versions of that room for 17 years, across Digital Transformation Offices, Cloud Transformation Offices, and Agile Transformation Offices, and the arc is always the same. Bright executive, big mandate-shaped object, no underlying authority, glowing first review, restructure or quiet rename within twenty-four months. The work that mattered, when it happened, happened in the line.

This article is about why the AI Transformation Office is the worst version of that pattern, why creating one is itself the diagnostic, and what the credible replacement looks like.

The Pattern Is Older Than AI

Before we touch AI, look at the arc of three prior transformation offices. The arc is the same.

Digital Transformation Offices, 2014 to 2019. Every Fortune 500 stood one up. McKinsey published the playbook. Recruiters built practices around the Chief Digital Officer seat. The promise was clear. The execution was uneven. By 2021, more than half of the original CDO appointments had been removed, restructured, or merged into the CIO or CMO. The actual digitisation of operating models eventually happened in the line, not in the office. The office mostly absorbed political risk during the transition.

Cloud Transformation Offices, 2018 to 2022. Same blueprint. Same vendor partnerships. Same five-year roadmap. The companies that actually moved to cloud were not the ones with the biggest Cloud Transformation Office. They were the ones whose CIO and CFO sat down and decided that the data centre lease would not be renewed. The office, where it existed, mostly slowed the move down by building governance scaffolding around a decision that had not yet been made.

Agile Transformation Offices, 2020 to 2023. Same pattern, smaller scale. The companies that actually got faster did so because individual product groups were given P&L authority and the freedom to staff their own teams. The Agile Transformation Office, in most cases, became the place where the line went to ask permission, which is the precise opposite of agility.

The pattern is not a coincidence. Every one of these offices started with the same logic. The technology shift is too important to leave to the line. Centralise it. Add a senior leader. Build a roadmap. Govern it carefully. Wait for value.

Every one of them produced the same outcome. The office became the bottleneck it was created to remove. Centralisation slowed the line. The slowness was confused for governance. Governance was confused for transformation.

I am not saying every transformation office is harmful. The good ones, in my experience, were tiny, short-lived, and explicitly disposable from day one. The bad ones were, and are, structural.

The Four Functions a Transformation Office Actually Performs

If you observe a typical Transformation Office for a year, four functions show up in the calendar. None of them is transformation.

Function one: optics. The office produces the artefact that the executive committee shows the board, and the artefact the board shows analysts. Strategy decks, capability heat maps, value tree diagrams, North Star metrics, McKinsey-style two-by-twos. None of these change a single workflow. All of them are essential to the political function of the role.

Function two: blame absorption. When AI underperforms, the post-mortem needs somewhere to land that is not the CEO and not the line. The office is a clean target. This is the same dynamic I unpacked in Most Chief AI Officers Are Hired to Fail at the executive layer. The office is the org-chart version of the same insulation.

Function three: vendor management. Most Transformation Offices end up running de facto procurement for AI vendors. Three RFPs in flight at any time. A "preferred vendor framework." A governance committee that meets monthly. This is not transformation. It is purchasing. The Build vs. Buy vs. Partner decision should not be a centralised committee output. It should be a unit-level commercial choice. The Build vs. Buy vs. Partner tool exists because that decision needs to happen at the unit level, not at the office level.

Function four: speed control. This is the one nobody writes on a slide. The office becomes the place that slows the org down enough that nothing breaks visibly. Every initiative routes through the office. Every initiative gets queued, prioritised, governed, and softened. The result is that the obvious wins land slower than they would have under unit ownership. The harder wins do not land at all.

These four functions can be valuable. But none of them is transformation. The office is, in practice, a containment structure for the ambition that the rest of the org was supposed to deliver.

The Structural Reason It Cannot Work for AI

Even if you accept that prior transformation offices were mixed at best, you might believe AI is different. It is. It is worse.

The reason is clock speed.

A Transformation Office operates on the timeline of the modern enterprise. Annual planning cycles. Quarterly steering committees. Eighteen-month roadmaps. Multi-year programme structures. These cadences exist for good reason. They allow alignment, governance, and accountability across a complex organisation.

AI capability does not respect those cadences. METR's 2025 Time Horizon work documents that the complexity of tasks frontier models can complete autonomously is doubling roughly every three months. Vendor pricing is moving on a similar curve. Open-source releases are landing on weeks. Architectural patterns that were correct in February are obsolete by August.

You cannot govern a three-month doubling curve with an eighteen-month roadmap. The two clocks cannot share the same operating model. One of them has to win. In practice, the office wins the political fight and the technology wins the actual contest. The office produces beautiful artefacts about a generation of capability that no longer exists. The line, frustrated, either deploys without the office or stops trying. The 95% pilot failure number documented by MIT Sloan in 2025 is partly a symptom of this mismatch. By the time the centrally governed pilot reports, the model has moved on.

I unpacked the pilot version of this dynamic in AI Pilots Are a Form of Procrastination. The Transformation Office is the org-design version of the same pathology. Both create the appearance of motion at a cadence the technology has already left behind.

The Centre of Accountability Trap

There is a second structural problem that is, in some ways, more damaging than the clock-speed mismatch. It is the centre of accountability trap.

When a CEO appoints a senior leader and an office to "own AI for the group," every line executive in the room reads the same signal. AI is the central team's problem. My problem is the quarter. If the central team's AI work helps me, I will accept the help. If it does not, I am not on the hook.

That signal is fatal for distributed AI. AI does not deliver value as a horizontal capability bolted onto the org. It delivers value when individual operators, in individual workflows, change how the work is done. The change is local. The accountability has to be local. If it is centralised, it is, by definition, not local. So nothing local changes.

I have watched this play out in multiple groups. Brilliant central AI team. Beautiful playbooks. Real platform investments. Almost no measurable change in the line, because the line was waiting. The central team had absorbed both the credit and the responsibility. The line had absorbed neither.

This is not a leadership failure. It is a structural failure. The org chart told the line the truth, even when the comms told them something else.

What Actually Works: The Dissolution Model

If centralised offices fail at this particular technology shift, what is the alternative?

The alternative is what I have come to call the dissolution model. It has three structural elements and one cultural element. None of them are subtle.

Element one: a 90-day catalyst team with a hard sunset clause. Yes, you do need a small central team in the first quarter. The job of that team is not to govern. It is to start fires. Five to ten of the best operators in the company, on full-time secondment, with explicit authority to bypass normal governance for the duration. The team has a single deliverable: three production AI workflows in three different business units, each tied to a real P&L outcome, by day 90. On day 91 the team disbands. The leader rotates back to a line role with a P&L. There is no extension clause. There is no "phase two." The sunset is the point.

Element two: P&L-embedded AI leads in every business unit. The work that the catalyst team starts has to be owned by someone with a P&L. That someone is named on day one. They are not "AI champions." They are not part-time. They are an operator with a number, and AI is one of the levers they have to move that number. They report to the unit head, not to a central function. They have a budget that comes out of the unit's P&L, not out of an "innovation" line. They are accountable for the unit-economics impact, not for "AI activity."

Element three: a board-level scorecard tied to retired roles and changed unit economics. The single most powerful intervention a board can make is to refuse to accept "capability built" as a metric. Demand two numbers, by unit, by quarter. How many roles have been retired or reshaped because of AI. By how much have the unit economics moved. Anything else is a slide.

The cultural element: the central team must be visibly disposable. This is the part most companies cannot bring themselves to do. The first announcement of the catalyst team must include the date of its dissolution. The team must be funded for that period only. The leader must accept the role on the explicit understanding that it ends. Anything less and the team will, like every other transformation office before it, find reasons to extend, expand, and entrench. The dissolution is the discipline that makes the model work.

A useful starting point for any board considering this path is the AI Readiness Assessment, which surfaces whether the operating model is actually capable of absorbing distributed AI, or whether the underlying gaps would force a centralisation reflex regardless of intent.

A Diagnostic for Boards and CEOs

If you are on a board or in a CEO seat being asked to approve an AI Transformation Office in the next 90 days, run the proposal through these six questions before you sign.

  1. Does the proposal include a named dissolution date for the central office, in writing, before any hires are made?
  2. Are the AI leads in each business unit named, P&L-accountable, and reporting to the unit head, not to the central office, on day one?
  3. Is the central office's budget separate from the units' AI budgets, and capped at the dissolution date?
  4. Is the board scorecard tied to retired or reshaped roles and unit-economics deltas, not to "capability built" or "use cases identified"?
  5. Does the office have explicit authority to bypass normal governance during its life, or will it route through the same committees that produced the bottleneck you are trying to solve?
  6. Is the proposed office leader willing to accept the role on the explicit understanding that the role ends?

If the answer to any of these is "we will figure that out later," do not approve the office. Tell the proposer to come back when the answers are yes. Most will not come back. That is the point.

What Boards Should Actually Be Asking

The honest version of the AI transformation conversation is harder than approving an office. It is harder than approving a roadmap. It is harder than approving a budget.

It is, in plain language, this. Are we, as a board, willing to demand that every business unit retire roles, change unit economics, and absorb AI into their P&L over the next three years, on a quarterly scorecard, in public, inside the company? If we are not, then no Transformation Office will compensate for the absence of that demand. If we are, then most of what a Transformation Office is supposed to do becomes unnecessary.

I have watched the Transformation Office reflex absorb three prior technology transitions. Digital. Cloud. Agile. In each case the offices outlived their usefulness by years and the actual transformation was eventually delivered, often in spite of them, by operators in the line.

AI is moving faster than any of those three. The window in which a containment structure can pretend to be a leadership structure is shorter. The cost of pretending is higher.

The Question I Would Sit With

The Madrid leader I opened with is still in his role. The office has expanded. The deputy has a deputy. The workstream count has grown from twelve to nineteen. The executive committee still loves the readouts. Two of the original three "lighthouse" use cases have been quietly de-scoped. None of them are in production. The legacy processes they were meant to replace are all still running.

He is not failing. He is being failed by a structure that was designed to look like a transformation rather than to produce one.

If you are on a board, or in a CEO seat, or about to accept a role leading an AI Transformation Office, here is the question I would put to you in plain language.

Are you building a transformation, or are you building the appearance of one?

Look at the six questions above. Count the yes-answers you can defend in front of your shareholders. The number you can honestly defend is also the answer to that question.