Why Your Change Initiative Stalled Before It Started

You launched it properly. Senior leadership was aligned. There was a kick-off event, a communication plan, a clear owner. Three months later the energy has leaked out, the initiative is still technically "running," and everyone has quietly returned to their previous behavior.

The cause is rarely execution. It usually sits in the architecture: the decisions made before the initiative started that determined whether it could ever work.

Here is what the research on organizational change shows, and what it means for leadership teams trying to do something real.

Most organizations are running too many changes at once

Warner Burke's research surfaces a pattern that will be familiar to anyone managing a growing company: the crowding-out effect.

When an organization runs four, six, eight change initiatives at the same time, none of them get enough oxygen. People can't hold it all in their heads. The initiatives compete for attention, calendar space, and emotional bandwidth. Leaders respond to the loudest crisis rather than the most important shift. Execution fades, not because people don't care, but because the system is asking too much of them at once.

One of Burke's clients described it plainly: "If we have just one more change effort in this plant, the whole place is going to sink into the ground."

The instinct of most leadership teams is to respond by adding coordination: a PMO, a change tracker, a dashboard. That makes the problem worse. The fix is fewer initiatives, which means deciding what to stop, not what to track better.

If your OKRs aren't landing, there's a reasonable chance the framework is fine. OKRs are simply the twelfth thing on the list, and they have no air.

Change and transformation are not the same work

The literature draws a line that most practitioners gloss over: the difference between change and transformation.

Change is single-loop. You correct the error without questioning what's producing it. You improve the process, refine the structure, tighten the cadence. The company's identity stays the same, and you run the same system more efficiently. This is legitimate, necessary work, and most of the time it's what a company needs.

Transformation is double-loop. You question the norms and values beneath the behavior. You change how the system understands itself. The metaphor from the OD literature is exact: freeing a caterpillar from a jar improves its situation but doesn't change its nature. Transformation is what happens when the caterpillar becomes a butterfly.

The practical problem is that most leadership teams say they want transformation and then design for change. The cause is rarely dishonesty. Teams underestimate what transformation costs. It requires leaders to question their own assumptions, not just their processes. It requires real discomfort at the top, sustained over time. It requires letting go of how things have always been done, including the patterns that made the company successful.

The diagnostic question is simple: has your leadership team had an honest conversation about what they are personally willing to change? Not the product, the org structure, or the roadmap: themselves. If not, the initiative is a change effort wearing transformation language, and naming that gap before launch is worth the awkward hour it takes.

The phase that determines whether change survives is the one before launch

Burke calls this pre-launch, and he argues convincingly that most change efforts fail because the foundation is never properly built.

Pre-launch is less about planning than about the leader doing three things.

First: self-examination. Leaders need to understand their own tolerance for ambiguity, their need for control, and how their personal patterns show up under pressure. A leader who asks for more autonomy in the organization but micromanages the first sign of deviation will kill the initiative faster than any external obstacle.

Second: building the honest case. Not the polished business case, the real one. Why is this change necessary now? What is the cost of not changing? What external reality is forcing the issue? When leaders can answer with specifics rather than abstractions, urgency stops being manufactured and becomes shared.

Third: clarity on what success looks like. Not a vision statement. A behavioral description of what will be different in 12 months: what decisions will be made differently, what conversations will start happening, what will have stopped.

There's an old OD adage: when anything goes wrong in a change effort, you can usually trace it back to this phase. That's hard to hear after the fact, and useful to design for before you start.

Why energy drops three months in

The post-launch fade is the most common failure pattern in change work. Leadership teams read it as failure. Often it means the opposite.

Heifetz's research on adaptive leadership identifies three things leaders need to sustain after launching a change.

Persistence. Change requires sustained, visible attention from the top for longer than feels proportionate. The moment leadership signals it has moved on, everyone else does too.

Holding the right level of pressure. Adaptive challenges require discomfort. People have to do things that don't feel natural yet. Push too hard and they shut down; not hard enough and nothing changes. The calibration is the work.

Managing avoidance mechanisms. This is the one most leaders miss. When change is reaching the layers that need to shift, the system pushes back in predictable ways: blame, scapegoating, deferring to authority figures for answers. These behaviors signal progress being resisted, not proof that the change is wrong.

The three-month dip is usually the system meeting its first real friction. What leaders do in that moment decides whether the initiative survives or quietly joins the list of things that were tried.

What this looks like in practice

The organizations that handle change well share a few habits. They choose fewer initiatives and hold them longer. They design the pre-work as carefully as the launch. They treat post-launch silence as a signal to stay engaged rather than to move on. And they've had an honest conversation at the leadership level about whether they're running change or transformation, because the answer changes how they build, measure, and sustain the work.

The companies that struggle start with too much, skip the foundations, and read the three-month dip as proof it didn't work. Most of the time, it never got the chance to.