Transformation programmes tend to begin with visible signs of progress.
A new platform is introduced. A transformation team is formed. Roles are created, workshops are scheduled and a governance structure appears on the organisation chart. There is movement, a sense of momentum and, for a while, genuine optimism.
The problems usually begin when the new model meets the existing company.
The previous approval process remains because removing it feels premature. The old technology is kept “for continuity”. Reports continue to circulate because senior management is used to receiving them. Teams are encouraged to adopt new ways of working while still being judged by the same targets, budgets and incentives.
Very little is actually retired.
Instead of replacing one operating model with another, the company starts running both.
The official organisation and the real one
Most companies can explain what their transformation is intended to introduce. Fewer can say, with the same precision, what will disappear once it has worked.
This distinction matters because organisations are shaped less by what leaders announce than by what employees encounter every day.
A company may promote faster decision-making while requiring several layers of approval. It may encourage experimentation while treating unsuccessful tests as management failures. It may install a central customer platform while allowing local teams to keep their own spreadsheets and reporting habits.
People notice these contradictions quickly.
They learn which process carries real authority, which metric affects their career and which system they still need in order to get the work done. The official transformation may be visible in presentations, but the older model often remains embedded in budgets, incentives and informal relationships.
From the employee’s perspective, this is not resistance to change. It is a reasonable response to mixed instructions.
Why companies find it easier to add than remove
Launching something new feels constructive. Removing something is more difficult because it creates an identifiable loss.
Ending a report means telling someone it is no longer useful. Simplifying an approval process means reducing someone’s control. Closing an old product or service may affect revenue. Retiring a familiar system can expose gaps that the organisation would rather not confront.
Addition also spreads responsibility. A new initiative can be announced collectively and presented as progress. Removal requires a decision, an owner and, often, a willingness to disappoint someone.
As a result, many transformation programmes leave the most politically difficult questions untouched.
The company redesigns the future without properly dealing with the interests, routines and sources of authority attached to the present.
Over time, this produces a kind of organisational debt. Employees maintain several systems, attend additional meetings and translate information between old and new formats. Managers spend more time navigating exceptions. What began as an effort to create capacity gradually consumes more of it.
The contradiction is felt most strongly in the middle
Senior leaders usually encounter transformation through steering committees, progress reports and milestone reviews.
The rest of the organisation experiences it as extra work.
Teams are expected to deliver the current business while learning new tools, following new procedures and contributing to new initiatives. Their previous responsibilities rarely disappear at the same pace.
Middle managers are left to make the two systems coexist. They have to protect delivery, interpret broad strategic ambitions and resolve conflicts that were never settled at leadership level.
When progress slows, they are often described as blockers. Sometimes that criticism is justified. In many cases, however, they are simply the first people to see that the proposed model cannot fit into the organisation without something else being removed.
A credible transformation should therefore answer two questions with equal seriousness: what must people begin doing, and what will they no longer be expected to do?
Without the second answer, change becomes another layer of labour.
Implementation is not the same as replacement
Transformation roadmaps are generally built around implementation milestones. The new platform goes live. Training is completed. Governance is established. Data is migrated. A revised operating model is published.
These steps matter, but they do not necessarily tell us whether the company has changed.
A platform can be live while the old one remains indispensable. Employees can complete training without using the new process. A governance committee can meet regularly without gaining any meaningful authority.
A better test is to ask what has become unnecessary.
Has manual work disappeared? Have duplicate systems been closed? Are decisions being made more quickly? Is ownership easier to understand? Have some meetings, reports or approval stages been removed?
The same question applies beyond technology.
A repositioning should make certain products, partnerships or communications clearly inappropriate. An organisational redesign should reduce ambiguity about who decides. A cultural transformation should change which behaviours are rewarded and which ones are no longer tolerated.
When everything that existed before remains necessary, the transformation has probably generated activity rather than replacement.
The missing stop list
Most transformation plans contain a roadmap. Very few contain a serious stop list.
The stop list is where the consequences of the transformation become visible. It might identify reports that will no longer be produced, tools that will be switched off, approval stages that will be removed, meetings that will be cancelled or services that the company will stop offering.
It may also deal with less tangible issues: metrics that will no longer determine performance, decisions that will move closer to operating teams, or behaviours that senior leaders themselves will need to abandon.
This is usually where the difficult conversations begin.
A company cannot become more focused while protecting every legacy activity. It cannot speed up decisions while retaining every control. It cannot ask managers to experiment while demanding certainty from every investment.
There will be trade-offs. Some people will lose authority. Some teams will have to change how they measure success. Certain sources of revenue may become less important. Temporary disruption may need to be accepted.
Avoiding those choices does not make the transformation smoother. It merely postpones the conflict until implementation, when it becomes harder to resolve and easier to blame on the organisation.
The old model may have worked very well
Legacy systems are not always irrational or badly designed. Many were created for good reasons and served the company successfully for years.
A centralised decision model may have protected quality when the organisation was smaller. A complex approval process may have emerged after a serious failure. A profitable product may still contribute meaningful revenue even if it no longer fits the company’s intended direction.
This history gives the old model legitimacy.
It also makes change personal. Questioning an established process can feel like questioning the judgement of the people who created it. Asking the organisation to move on may sound like a dismissal of the work that produced earlier success.
Leaders need to handle this carefully.
The useful message is rarely that the previous model was wrong. More often, the circumstances that made it effective have changed. The company is larger, the market is different, customers expect something else or the economics no longer work in the same way.
That distinction makes it possible to respect the past without allowing it to determine every future decision.
Leadership has to accept the cost of transition
Employees are often less opposed to transformation than leaders assume. What they struggle to understand is whether management is genuinely prepared to accept its consequences.
Will the company tolerate a short-term drop in efficiency while a new system is learned? Will executives give up approval rights? Will teams be evaluated differently? Will profitable but distracting activities be closed? Will leaders stop asking for the reports and reassurances produced by the old model?
These decisions reveal more than any internal communication campaign.
Leadership commitment is not demonstrated by repeating the ambition. It is demonstrated by protecting the choices that make the new model possible, particularly when those choices create discomfort.
When leaders continue to demand the speed of the new system and the certainty of the old one, employees receive an impossible instruction: change the organisation, but preserve every outcome, habit and safeguard that defined it before.
Change should eventually make the company easier to run
Some transformations need additional resources at the beginning. New capabilities have to be built before older ones can be removed. For a period, duplication may be unavoidable.
But it should remain a transition, not become the permanent operating condition.
The company should know which decisions are expected to become faster, which activities will disappear, where responsibilities will become clearer and what capacity will eventually be released.
Otherwise, the organisation remains suspended between two models: one it no longer fully believes in and another it has not yet authorised.
Transformation is complete only when the new way of operating no longer depends on the structures it was supposed to replace.
That moment rarely comes from launching one more initiative.
It comes when the company is finally willing to let something end.
Moon Above Advisory works with leadership teams at moments when the organisation needs to evolve, but the direction and trade-offs are not yet fully defined.
Discuss a transformation mandate →