Why transformation programmes stall after the first push

Most transformation programmes start well.

There's energy. Senior sponsorship. A clear mandate. A capable programme team. The first few months move quickly — workshops, diagnostics, roadmaps, early wins. Leadership feels the momentum and assumes the hard work is done.

Then, somewhere around month four or six, things slow down. Delivery becomes harder to track. Teams start reverting to old patterns. The programme team is still working flat out, but the organisation isn't really changing.

This is the stall. And it's almost always the same pattern.

What causes it

The first push of a transformation works because it relies on energy, novelty, and visible leadership attention. Change happens because people are excited, paying attention, and feeling watched.

That's not sustainable. And it doesn't embed anything.

The real work of transformation is changing how the organisation operates — not how it feels during a kickoff workshop. That requires different things: clearer ownership, changes to how decisions get made, adjusted incentives, and new ways of reviewing progress that connect what teams are doing to what leadership actually cares about.

Most transformation programmes are designed for the first push. They don't build the operating system that sustains change after the energy fades.

The three patterns I see most often

Pattern one: The programme team does the work instead of building capability.

When a programme team is staffed with capable people, they naturally step in to make things happen. They run the workshops. They draft the strategies. They track the progress. This produces output — but it doesn't transfer capability into the organisation. When the programme ends, there's nothing left to hold the change in place.

Pattern two: There's no clear owner at the right level.

Transformation requires someone with authority to make decisions, resolve conflicts, and shift resources. That person is usually named in governance documents but rarely empowered in practice. They're too busy with their day job. The programme becomes a parallel workstream rather than a genuine reorganisation of how the business operates.

Pattern three: Progress is measured in activities, not outcomes.

Milestones are hit. Workstreams are on track. RAG statuses are green. But the outcomes — the things that were supposed to change — aren't being measured. Nobody knows whether customer experience has improved, whether delivery is faster, or whether the operating model is actually working differently.

Activity measurement creates the illusion of progress. It doesn't tell you whether the transformation is working.

What actually makes transformation stick

Change sticks when it becomes the new normal — not when it's delivered as a programme.

That means building the capabilities, rhythms, and ownership structures that allow the organisation to operate differently without a programme team holding it together.

In practice, this looks like:

Clear ownership in the line. Every change that matters should have a named owner in the business — not in the programme. That person is accountable for the outcome, not just for completing the workstream.

Outcome-based progress reviews. Replace activity reporting with genuine outcome tracking. What has changed? How do we know? What are we learning from what isn't working yet?

Operating rhythm changes. Transformation that doesn't change the leadership calendar doesn't stick. If the organisation reviews performance the same way it always has, it will drift back to the same behaviours.

Honest staging. Most programmes try to do too much at once. A tighter scope, sequenced deliberately, creates better conditions for real change than a broad programme that spreads energy too thin.

The uncomfortable question

If your transformation programme is six months in and the energy is fading, the question worth asking is: what would this organisation look like if we stopped the programme tomorrow?

If the honest answer is "mostly the same", that's the signal. The change hasn't been built into how the organisation operates. It's been layered on top.

The first push is the easy part. The hard part is designing for what comes after it.

That's usually where I come in.

---

If your programme is stalling and you're not sure what's causing it, the Strategy to Execution diagnostic is a useful starting point — it shows where the system gaps are across strategy, portfolio, delivery, and performance.