Transformation has become one of those words that organisations use so often that it has almost stopped meaning anything.
There are transformation offices, transformation directors, transformation roadmaps, transformation workstreams and transformation steering committees. There are budgets large enough to frighten a small government and delivery plans detailed enough to suggest that the future has somehow been reduced to a sequence of milestones.
And yet, several years later, the organisation is often still operating in much the same way it did before.
The technology may be newer. The org chart may have changed. A new operating model may have been launched with considerable ceremony. There may be dashboards where previously there were spreadsheets. But decisions still take too long, the same people still have to approve everything, funding still follows cycles that make experimentation difficult, and underperforming products and systems still survive because nobody wants to make the decision to kill them.
The organisation has changed a great deal without actually becoming very different. That is the problem with treating transformation as a programme.
A programme has a start date, an end date, a budget and a definition of done. Those things are useful when you are building something discrete, replacing a platform or moving from one known state to another. They are much less useful when the objective is to change how an organisation behaves, because behaviour does not fit neatly into a delivery plan.
Real transformation is not the completion of a collection of initiatives. It is a permanent change in the way the organisation operates.
That means changing how decisions are made, how money is allocated, how priorities are set, how products are funded, how risk is understood and how quickly teams can act. It means changing how success is measured and, just as importantly, how readily the organisation stops doing things that no longer make sense.
That last part is where most transformation efforts become uncomfortable.
Organisations are generally much better at adding than removing. They add governance forums, reporting layers, platforms, processes, roles and oversight mechanisms. Each addition usually has a perfectly reasonable explanation on its own, which is how organisations eventually end up with an operating model that resembles geological sediment.
The harder work is removal. Meetings that no longer need to happen. Approvals that no longer add value. Systems that should be retired rather than modernised. Products that should stop receiving investment. Organisational boundaries that exist mainly because they have always existed.
Those decisions are difficult because removal creates losers. It changes authority, exposes choices that have previously been avoided and sometimes requires leaders to admit that something which once made sense no longer does. That is politically harder than buying a new platform, hiring a consultancy or launching another workstream, so organisations often choose the easier version of transformation instead.
They change the visible machinery while leaving the underlying incentives and decision structures intact.
Technology is replaced, but ownership remains fragmented. Teams are reorganised, but funding still discourages long-term accountability. Agile methods are introduced, but every significant decision still travels through the same hierarchy. New data platforms are built, but nobody changes who is accountable for the quality or use of the data.
From the perspective of the programme, this can still look like progress. Systems have gone live, workstreams have closed, people have moved into new structures and the dashboard contains a reassuring quantity of green.
This is why transformation programmes can be simultaneously successful and useless. They can hit milestones, deliver systems, close workstreams and come in close enough to budget for everyone involved to describe the experience as a success. None of those things, by themselves, demonstrate that the organisation has become materially better at operating.
A better test is whether the organisation has gained capabilities it did not previously have.
It should be able to make important decisions faster, redirect investment when circumstances change, give teams accountability for outcomes rather than outputs, and evolve technology without requiring another enormous intervention. It should also be better at stopping work that no longer has value, because an organisation that can only start things is not particularly adaptable.
Most importantly, transformation should change the conditions under which leaders exercise judgement. If every significant decision still requires the same layers of protection, escalation and committee approval, then the organisation may have modernised its systems without modernising the way it thinks.
The uncomfortable truth is that genuine transformation rarely ends cleanly. There is no useful moment where an organisation can declare itself transformed and return to business as usual, because business as usual is the thing that was supposed to change.
Capabilities improve, decision structures evolve, platforms are replaced and old constraints are removed. New constraints appear, because they always do, and the organisation keeps adapting because the environment around it keeps changing.
That is less satisfying than a programme with a launch event, a branded slide deck and a completion date. It is also much closer to reality.
Transformation should not be something an organisation periodically does to itself. It should become part of how the organisation operates, because if another major transformation programme is required five years later, there is a reasonable chance the last one changed the furniture rather than the organisation.