September 14, 2026 • 6 Min Read

But the business is quietly telling a different story. Regional finance teams are still closing the books differently. Employees have built workarounds into some of the new processes. And as AI takes on more of the work involved in gathering and reconciling information, questions are emerging about where human judgment belongs and whether controls designed around the old workflow still make sense. 

Nothing has obviously failed. Each team can point to progress. Yet the company is not becoming the more integrated finance organization the transformation was intended to create. 

What has broken down is not necessarily the transformation plan. It is the organization’s ability to keep its parts moving together as that plan becomes reality. Transformation depends on far more than completing individual initiatives. The enterprise has to continually synchronize how decisions are made, how work gets done and how new capabilities are absorbed into the business. When that stops happening, even well-executed workstreams can add up to a transformation that is going nowhere. 

Alignment Is Only the Beginning

Most transformations begin with broad agreement about what needs to change. The harder test comes later, when that ambition has to guide hundreds of decisions throughout the organization.

A 2026 Harvard Business Review article calls this the “false alignment trap.” Its authors argue that leadership teams can believe they agree on why, what and how to change while important differences in assumptions remain unresolved. Those differences often surface only when people have to decide how the transformation will actually work.

That is what happens at our manufacturer. Leaders in one region understand standardization to mean following a common global process unless there is a compelling reason to deviate. Another region assumes established local practices will remain wherever leaders believe they work better.

Neither group considers itself resistant to the transformation. Both believe they are executing it.

The problem is that the organization no longer has one shared interpretation of what the transformation requires. As those choices accumulate, the regions begin creating different versions of the future business.

This is why alignment at the beginning of a transformation is not enough. The organization has to remain synchronized while the transformation unfolds.

AI Raises the Stakes

That ability is becoming more important as AI enters transformation programs.

AI can alter how a workflow operates almost immediately, but the implications rarely stop with the technology itself. As automation changes where work is performed, judgment may move to a different point in the process. Responsibilities can shift. Existing controls may need to be reconsidered.

Gartner reports that 78% of CHROs expect workflows and roles to change as organizations seek to capture value from AI investments.

The faster these changes move through the business, the harder it becomes for an organization built around relatively independent functions and workstreams to absorb them coherently. A decision made in one place can create consequences elsewhere before the rest of the organization has had time to adapt.

That makes the real challenge of transformation increasingly clear. It is not simply executing every part of the program successfully. It is maintaining the connections that allow the enterprise to evolve as one functioning whole.

Follow the Friction

Leaders can often see the first signs of that breakdown in places traditional program reporting misses.

An experienced employee creates a spreadsheet workaround because the new process does not fit an important exception. A decision gets escalated repeatedly because two leaders both believe they own it. A regional team finds that the standardized process produces a result that makes sense globally but creates problems locally.

Those moments can look small. They are often treated as implementation issues to be resolved and moved past.

But they may be telling leaders something more important: the transformation design and the way the organization actually operates have begun to separate.

Workarounds are particularly revealing. They are often interpreted as resistance, yet sometimes employees are compensating for a disconnect the transformation itself created. Before trying to eliminate the workaround, leaders should understand what problem it is solving.

The same applies to recurring escalations. When decisions continually rise through the organization, it may signal that work has changed faster than the authority surrounding it.

Gartner’s research reinforces the importance of listening to those signals. Organizations that regularly adapt their change plans based on employee response are four times more likely to achieve successful change. The lesson is not that transformation should constantly bend to employee preference. It is that what happens in the operating environment provides valuable information about whether the organization is adapting as a whole.

Restore the Connections

Getting the transformation back on track therefore begins with finding the point where the organization stopped moving together.

For our manufacturer, that may mean resolving what standardization actually requires rather than allowing each region to interpret it independently. If a process is producing widespread workarounds, leaders need to understand whether the behavior or the process should change. If technology has altered how work happens, the organization may need to rethink who makes certain decisions rather than simply expecting the existing structure to absorb the change.

This is also where governance becomes more than program oversight.

Its most important role may be resolving the issues that fall between organizational boundaries — problems that do not belong neatly to technology, finance, HR or a particular region because they arise from the way those parts interact.

Good governance gives leaders a place to make those connections visible and resolve them around the enterprise outcome, rather than allowing every part of the organization to optimize independently.

The goal is not to force every function to operate identically. It is to ensure that different parts of the business are still contributing to the same outcome and adapting together as circumstances change.

Because when every workstream is green but the transformation is red, the problem is often that somewhere along the way, the organization stopped moving as one.