On the difference between transformation and expensive change, and why it matters.
Every large organisation has one. A programme with "transformation" in its title, a director appointed to lead it, and a budget that makes the board wince slightly before approving it. The slide deck promises a new way of operating. The town halls speak of bold ambition. And somewhere in the middle of all of it, a large number of intelligent, hardworking people get on with the work.
Three years later, the question nobody quite asks out loud: did we actually transform?
This is not a criticism of the people involved. It is an observation about the word itself, and the trouble that starts when organisations reach for it before they have really defined what they mean.
The word is doing too much work
Transformation has become a budget category. It sits alongside "innovation" and "digitalisation" as language that signals ambition without committing to a specific outcome. It is the word that gets programmes funded, directors appointed, and workstreams initiated, often without a clear answer to the most important question: what will be fundamentally different about how this organisation creates and delivers value when we are done?
That question is harder than it looks. It requires a level of honesty about the current state that is uncomfortable. It requires agreement at the top of the organisation, which is rarer than it should be. And it requires a willingness to sit with uncertainty about the destination, which does not sit comfortably inside most governance frameworks.
So instead, organisations define the programme. They scope the workstreams. They hire the consultants. And they call it transformation, because the aspiration is real, even if the definition is not yet sharp enough to hold the whole thing together.
What transformation actually means
The standard is higher than most programmes reach, and that is worth being honest about.
Genuine transformation means the organisation that exists at the end is fundamentally different from the one that started. Not faster. Not leaner. Not better at what it already does. Different, in a way that matters, in how it competes, how it creates value, or how it operates at its core.
By that standard, most large-scale change initiatives, however significant, however well-funded, however sincerely intended, are not transformations. They are improvement programmes. Important ones, sometimes essential ones, but not transformation.
This distinction is not pedantic. It changes what you plan, how you govern it, what success looks like, and whether you end up with what you actually needed.
The three common labels, and what they actually mean
Business transformation is the broadest term and, used correctly, the most demanding. It touches operating model, commercial model, culture, structure, and strategy. It typically begins with a strategic imperative: a market that has shifted, a competitive position under threat, a performance problem that incremental improvement cannot solve. The answer, when it is genuine transformation, is that the business must operate differently at its core. Everything else, technology, digital capability, process redesign, enables that strategic intent.
Digital transformation became the dominant label of the last decade, and with it came most of the confusion. At its best, it describes something genuinely significant: using digital capability to change how value is created and delivered, not just how existing processes are executed. The test is whether the customer experience, the business model, or the operating model has materially changed as a result. At its worst, it describes digitising analogue processes and calling the result a transformation. Putting forms online is not transformation. Changing what those forms make possible might be.
Technology transformation is, in some ways, the most honest label of the three, because it is the most specific. It describes changes to the underlying estate: migrating away from legacy, modernising architecture, moving to cloud platforms, rationalising a sprawling portfolio of systems. It is enabling work. It can unlock transformation in other parts of the business, but it does not deliver that transformation on its own. The mistake organisations make is conflating the enabler with the outcome, and expecting business results from what is essentially technology modernisation.
The patterns worth recognising
There are a few patterns that appear consistently in programmes that struggle to land what they promised. None of them are unique to any one organisation, and naming them here is not intended as judgement. They are simply common, and recognising them is useful.
A programme structure designed for delivery rather than transformation. Gantt charts, workstream leads, RAG statuses, and milestone governance are well-suited to delivering defined scope on a timeline. They are poorly suited to a change where the destination is still being discovered, where the dependencies are human rather than technical, and where benefits realisation depends on adoption rather than delivery.
Culture treated as an assumption rather than a workstream. Almost every transformation programme acknowledges, somewhere in its narrative, that culture is important. Very few treat it with the same rigour as the technical or process components. Culture ends up as a change management workstream with a comms plan attached, rather than as the most significant constraint the programme faces.
Senior sponsorship that is visible but not active. Leadership endorsement, the slide with the CEO quote, the town hall appearance, is not the same as sustained leadership engagement with the hard choices the programme will surface. Transformation creates conflict, ambiguity, and competing priorities. Without leaders who are genuinely present in that, it stalls.
So let's reframe this …
The question is not whether transformation is worth pursuing. For many organisations, in many circumstances, it is the right answer, and when it is done well, the results are significant and durable.
The question is whether what is being called transformation has been set up to actually achieve it.
That starts with being honest about what kind of change is genuinely being attempted, and whether the label matches the intent. It continues with a clear articulation of what will be different at the end, specific enough that everyone can use it to make decisions along the way. It requires a theory of change that goes beyond a delivery plan, one that acknowledges the human, cultural, and leadership conditions that will determine whether the work sticks. And it needs governance that can hold both delivery accountability and the messier reality of organisational learning.
None of this is straightforward. If it were, the success rate for large transformation programmes would be considerably higher than it is.
But it starts with the word. With being honest about what is being attempted, and what that actually requires.
If you liked this article, you can find more insights from the team here
72 Degrees Consulting works with senior leadership teams on the design, governance, and delivery of complex transformation programmes. If you are at the start of a transformation, or questioning whether an existing programme is set up to succeed, we would be happy to talk.
No comments yet