Why transformation programmes don't fail on go-live day
There is a moment in most transformation programmes when the mood shifts. Go-live has happened. The system is running. The team that spent two years delivering it has been stood down or moved on. And somewhere between three and nine months later, a quiet realisation sets in: this isn't working the way it was supposed to.
The ERP is live, but people are still using spreadsheets for the things that matter. The new process has been designed, documented and trained — but the organisation is doing it the old way. The operating model has been signed off by the board, but decision-making is happening in the same informal channels it always did.
This is not failure. Not yet. But it is the pattern that precedes it.
The visible and the invisible
Every transformation has two parts. The visible part is what gets managed: the system implementation, the process redesign, the programme plan, the go-live milestones. These are measurable, deliverable, and governed. They are also, in most cases, the easier part.
The invisible part is what determines whether the visible work actually delivers the intended outcome: the leadership behaviours that need to shift, the decision rights that need to be clarified, the governance maturity that needs to be built, the middle management layer that has to translate strategy into daily operations, and the capability gaps that existed before the programme started and have not been closed.
Technology changes overnight. Organisations change much more slowly. When a programme treats the technology delivery as the transformation — rather than as the trigger for transformation — the gap between what was delivered and what was supposed to change becomes visible only after go-live. By then, the delivery team has gone, the budget has been spent, and the business is operating a new system in an old way.
Why this pattern keeps repeating
The pattern is not caused by incompetence. It is caused by a structural problem in how transformation is designed and governed.
Most transformation programmes define success as delivery. Scope, schedule, budget — the classic project triangle. Performance improvement is assumed to follow. The business case states what will be achieved; the programme plan describes how the technology will be delivered; and the connection between the two — the organisational changes that actually produce the improvement — is treated as an implementation detail.
When the performance improvement doesn't materialise after go-live, the causes are almost always the same: leadership behaviour didn't shift, governance wasn't redesigned to match the new operating model, capability gaps weren't addressed, and the middle management layer wasn't equipped to operate in the new system. None of these are technology problems. All of them were predictable.
The question that changes the outcome
The organisations that consistently deliver transformation outcomes ask a different question at the start. Not "can we implement this?" but "will this deliver the performance improvement it's supposed to, given the organisation we actually have?"
That question is uncomfortable. It may reveal that the capability gap is larger than the business case assumed. It may reveal that the governance model doesn't support the decision speed the new operating model requires. It may reveal that the organisation is not ready for the transformation it is planning — and that launching now, at full scale, will produce exactly the pattern described above.
But answering that question before committing resources is always less expensive than discovering the answer after go-live.
What this means in practice
Transformation that delivers its intended outcome is not fundamentally different from transformation that doesn't. The technology is similar. The process methodology is similar. The difference is in what was addressed before the programme started — and what was left until it was too late.
The organisations we work with that consistently deliver are the ones who spent time on the invisible part of transformation before it became expensive to ignore. They assessed the capability gap honestly. They designed governance that matched their operating rhythm. They equipped middle management to lead change, not just to receive it. They defined what success looked like in measurable performance terms — not just programme milestones.