Transformation should reduce friction. Too often it simply adds another layer on top of the old organisation.
Transformation is one of those words that can mean almost anything.
A new ERP is transformation. A restructuring is transformation. A cloud migration, operating-model review, automation programme or brand refresh can all be described the same way.
The danger is that organisations become very good at launching transformation programmes while becoming steadily harder to operate.
New governance is added without removing old governance. New systems arrive while legacy systems remain essential. New roles are created to coordinate the gaps between teams. Reporting increases because leaders no longer trust the underlying information.
The organisation has transformed, technically. It has also become more complicated.
Complexity has a carrying cost
Every process, system, approval, meeting, report and hand-off consumes attention.
Individually, each may be defensible. Collectively, they can make an organisation slow.
The cost is not only financial. Complexity reduces decision speed. It makes accountability harder to see. It creates more places for information to be lost. It encourages capable people to spend time navigating the organisation instead of improving it.
A transformation programme that adds capability without removing complexity may still be worthwhile. But if nothing is retired, simplified or clarified, the business eventually pays for both worlds.
Start by identifying what can disappear
One of the most useful questions in transformation is not “What should we add?”
It is “What should no longer exist when this is finished?”
Which spreadsheet disappears? Which approval is removed? Which manual report is no longer required? Which system can be retired? Which duplicate team hand-off ends? Which meeting becomes unnecessary because the information is available automatically?
That creates a much more demanding definition of success.
The new thing is not complete when it is launched. It is complete when the old friction has actually gone.
Design around decisions
Many processes exist because a decision needs to be made.
Who can approve this? What information do they need? What threshold changes the route? What evidence needs to be retained?
If you design around the decision rather than the historical process, the workflow often becomes simpler.
The same principle applies to reporting. Leaders rarely need more reports. They need confidence that the right signals will be visible early enough to act.
Transformation should make important decisions easier, faster and better informed.
Do not confuse standardisation with improvement
Standardisation can be powerful, especially across a growing organisation. But forcing every team into the same process can also preserve bad assumptions at scale.
The purpose of a standard is to make good work repeatable.
It should not make exceptions impossible or local expertise irrelevant.
The right question is whether the standard improves outcomes while reducing unnecessary variation.
Transformation is an operating discipline
The best transformation work is not theatrical.
It is a series of practical decisions about how the organisation should work: what information exists, where it lives, who owns it, how work moves, what systems support it and what can be removed.
That is why I prefer transformation programmes with visible operating outcomes.
Fewer hand-offs. Shorter cycle times. Better data. Clearer ownership. Less duplication. Faster decisions. More capacity.
If the organisation looks more sophisticated at the end but feels harder to run, something has gone wrong.
Transformation should not leave a business with more to manage.
It should leave it with more ability to act.