I told the client this would fail catastrophically before they started. Not because the technology was wrong. Not because the vendor was incompetent. Because nobody owned the change.

They implemented anyway. They celebrated. Nobody had tested what success actually looked like in operational terms. The business was never part of the journey. The processes underneath were untouched. What they called a transformation was a lift-and-shift, chosen precisely because it required the least thinking and the least accountability from the people authorizing it.

The result was total collapse. Case volumes exploded. The client appeared in the press for the wrong reasons. And the people who had driven the project were gone before the invoice for the damage arrived. Not because better opportunities found them. Because the system never required them to stay and face what they had built.

They did not leave because they were bad professionals. They left because no one had designed a structure to keep them accountable when the lights went out.

The most dangerous decision in a transformation is not a technical one. It is the absence of a human one: who owns this when it goes wrong?

The ownership vacuum has four symptoms, and they appear together so consistently that their presence alone is diagnostic. There is no defined owner of the transformation itself. IT owns the technology, but nobody owns the change. Success is defined as go-live, which is not a business outcome but a project milestone that marks the beginning of the actual work, not its end. Current ways of working are never rationalized. New technology is placed atop old patterns and labeled a transformation. And change management exists as a line in a project plan that nobody is personally accountable for delivering.

When all four are present, the outcome is predetermined. The organization will spend money, produce activity, celebrate a date on a calendar, and return to roughly the same operational reality six months later. The technology will be live. Nobody will use it correctly. The gap between what was promised and what was delivered will be explained by factors that were knowable before the first contract was signed.

No serious athlete trains without knowing their starting point. No serious coach builds a program without measuring baseline performance, tracking progress continuously, and defining what success looks like before a single session begins. Remove the measurement structure, and you do not have a training program. You have expensive movement.

Three things must exist before a single euro of investment is authorized. A baseline: where is the organization today, measured in actual operational outcomes, not in platform maturity or technical readiness. A retrospective cadence: continuous measurement against that baseline throughout the entire journey, not a single post-go-live review conducted after the decisions that mattered were already irreversible. And a defined target: what specific operational result is this investment designed to produce, stated in terms a CFO can hold against actual outcomes twelve months after go-live.

Without all three, you are not running a transformation. You are running a project with a celebration built into the schedule and no mechanism to know whether anything has changed.

The client in the opening of this article had none of those three things. That is not unusual. It is the norm.

Prosci's research across thousands of change initiatives shows that projects with excellent change management are six times more likely to meet their objectives than those with poor change management. Not marginally more likely. Six times. That is not a soft advantage. That is a structural difference between organizations that build correctly and organizations that build quickly and then rebuild at greater cost.

McKinsey finds that when senior leaders personally model the behavior they are asking others to adopt and take genuine ownership of the transformation, success rates are 5.3 times higher than at organizations where leadership delegates the change and carries on with business as usual. Ownership is not a soft skill. It is the single variable with the largest measurable impact on whether a transformation produces anything beyond an installation.

BCG's analysis of more than 1,200 organizations identifies the top 5% of companies that are actually generating value from transformation. The characteristic they share is not their technology stack, their vendor relationships, or their budget size. It is a continuous measurement against a defined baseline. Not once at go-live. Continuously. Before, during, and long after the celebration ends, the accountability structures quietly dissolve.

Most boards and executive teams approve transformation budgets with the same information they would use to approve an office renovation. They see a plan, a cost, and a go-live date. They do not see the measurements that would tell them whether the investment worked.

Before you authorize the next transformation or AI installation, ask five questions.

Who owns the transformation, not the project, the transformation itself, and where does that ownership appear in the organizational structure with real accountability attached to it?

What is the definition of success beyond go-live, stated in operational and financial terms that can be audited against actual outcomes twelve months after the celebration ends?

Have you rationalized today's processes and ways of working, or are you adding new technology on top of old patterns and calling it progress?

Who is personally accountable for change management and adoption, with their performance measured against adoption rates and not deployment timelines?

And the fifth question, the one almost never asked before the budget is approved:

Who owns the financial consequences if it does not work? Not who owned the process. Who built the business case? Who is measuring actual outcomes against the projections that justified the investment?

In most organizations, the honest answer is nobody. The CTO drove the initiative. The CEO approved the direction. The CFO signed the authorization without a framework for measuring success or failure on the other side. That is not an AI problem. It is not a process problem. It is a capital allocation problem that has been dressed up as a technology problem for long enough that nobody questions the costume anymore.

The CFO's question when results come in below expectations should be direct: Why did we finance the operation before we checked the patient's vital signs?

If you look at your current implementation and find that it is missing a defined owner, clear operational outputs, rationalized processes, and a person whose career is accountable for adoption, do not proceed.

The technology will survive the delay. The organization may not survive another transformation that vanishes before it delivers.

The Intelligence Briefing publishes weekly for executives who want to understand why transformations fail before they fund the next one. Find it at intelligencebriefing.beehiiv.com