Why Change Programs Break Down Between Activate and Transform

Most transformation programs do not fail at the beginning. They break down in the middle, right when the organization has the least patience left.

Bain & Company's 2024 Transformation & Change Survey of more than 400 executives and senior leaders found that only about 12 percent of business transformations achieve their original ambition. That is a different question from whether the project got delivered. A system can go live on time, fully rolled out, technically a success, and the transformation can still fail, because the organization underneath it never actually changed how it operates. Eighty-eight percent fall short on that second, harder measure, and not from a lack of effort or investment. Bain's data points to a specific, repeatable pattern in how talent gets allocated once an initiative moves past its opening phase.

The clearest predictor Bain found wasn’t strategy quality or budget size. It was whether the company protected real time for the people doing the work. Two-thirds of strong transformers made sure the people assigned to the effort had at least half their working hours protected for it. Weaker performers routinely didn't. They stacked the transformation on top of someone's existing job and called the overlap resourcing.

That distinction describes almost exactly what happens between Activate and Transform in the PATH Framework, the four-phase execution structure inside the Momentum TransforMate Ecosystem (MTE): Prepare, Activate, Transform, Harness.

What Activate is actually built for

Activate is the launch. A kickoff, a communication wave, a first set of visible wins designed to build belief that the change is real. It is resourced for velocity: a small group of the organization's best people, borrowed briefly from their regular jobs, running hard for a defined burst.

That resourcing model works for a burst. It was never built to survive months of Transform.

Where Transform actually starts, and why the Activate team can't carry it

Transform is not a continuation of Activate. It is a different kind of work, and it usually runs on the exact same people, now stretched thinner. Bain's research names this pattern directly: more poor-performing transformations kept overloading their most capable people well past the point that was sustainable, the same people who carried Activate, still carrying Transform, with no additional time protected and no relief in sight.

Burnout isn't just a wellbeing problem when this happens. It is a resourcing failure with research to back it up: Bain found that dedicated ownership, a named leader accountable for the transformation, correlated with 24 percent more of the planned value actually getting delivered. Most Activate phases run without needing that kind of single owner. Momentum and executive attention cover the gap in the moment. Transform doesn't have that luxury. Without someone who owns the decisions once the launch excitement fades, the initiative drifts back onto whoever's calendar had the most room that week, usually the same overloaded people from Activate.

This shows up the same way across ERP rollouts, Agile transformations, and AI adoption efforts alike. The system goes live, the pilot team celebrates, and months later the actual usage data looks nothing like the business case that got the initiative funded. The difference between those two numbers is rarely a training problem. It is the resourcing and ownership model built for a launch, still running unchanged into a phase that needed something structurally different.

What the PATH Framework builds in structurally

The PATH Framework treats the move from Activate to Transform as a designed checkpoint, not a handoff that happens by default. Before a transformation is allowed to move into Transform, three questions get answered on purpose: who owns the decisions Transform will require now that Activate's borrowed time has run out, whose calendars actually have protected hours for this work instead of an unspoken expectation that it happens on top of everything else, and what capability the organization is building for the roles that will matter in two to three years, not just the ones the current job descriptions cover.

None of these questions is complicated to ask. They are easy to skip, because Activate's own success, the energy, the visible wins, the executive attention, makes it feel like the hard part is already behind the organization. Bain's data says the opposite: the companies that pull this off are not the ones with the most enthusiasm at launch. They are the ones that protected real hours, named a real owner, and kept building capability past the point where it was tempting to declare victory and move on.

Where is your organization actually positioned between Activate and Transform? A free starting point is the Organizational Adaptability Pulse Check.

If this pattern is one you recognize and want to talk it through directly, I am happy to have that conversation.