Most transformations aren't.
They're rebranding exercises with a project plan attached. They have steering committees, RAG status reports, and a launch event with a logo. They produce a lot of noise, consume a lot of budget, and leave the organisation broadly unchanged — except now it has a new operating model document that nobody reads and a change management workstream that was quietly wound down in month four.
I've been doing this work for over two decades. I've walked into organisations mid-transformation and had to diagnose why nothing is actually moving. The patterns repeat with remarkable consistency. So here, bluntly, is what I look for before I'm willing to say a transformation is real.
1. Can anyone tell me what won't change?
Every transformation programme will tell you what's changing. Slides full of it. But ask a senior leader what is not changing — what is protected, what is load-bearing, what they would rather break the programme around than break — and the answer is usually silence, or something vague about culture.
That silence is diagnostic. If an organisation hasn't identified what it's protecting, it hasn't understood itself well enough to change. Real transformation requires a theory of continuity, not just a theory of change.
2. Is the discomfort landing at the right level?
Change programmes that are working tend to make certain people uncomfortable. Specifically, the people whose current influence depends on things staying the way they are.
If everyone in the room is enthusiastic, I get suspicious. Either the programme isn't touching anything real, or the people it would disturb haven't been told the full story yet. The question isn't whether there's resistance — resistance is evidence that something real is happening. The question is whether leadership has the nerve to hold the line when it arrives.
3. Does the business case have a named owner — or just a sponsor?
Sponsors are common. They attend the kick-off, they lend their name to the programme, they show up at steering committees. What they rarely do is take personal accountability for whether the benefits actually land.
What I look for is something different — a Value Owner. Someone who has committed, explicitly and on record, to the specific outcomes the programme is meant to deliver. Not the technology delivery. Not the change management. The actual business outcome: the cost reduced, the revenue generated, the process time eliminated.
When a business case has a Value Owner, the governance changes. Decisions get made faster. Trade-offs get resolved at the right level. Scope that doesn't serve the outcome gets cut. When it doesn't, the business case is essentially a document, not a commitment. And documents don't deliver transformation.
4. Has governance been stress-tested, or just designed?
Most transformation programmes have governance frameworks. Terms of reference, escalation paths, decision rights. On paper they look robust. The question is whether anyone has deliberately tested what happens when the framework meets reality — a missed milestone, a budget overrun, a key dependency that a third party controls.
Governance that hasn't been stress-tested tends to be governance that exists to provide comfort, not to drive outcomes. The first time it's genuinely needed, it either seizes up or gets bypassed. At that point the programme is effectively running on goodwill and individual heroics — which is fine until it isn't.
5. Has leadership personally given something up?
This is the hardest question to ask and the most revealing. Transformation almost always requires someone at the top to relinquish something — budget control, headcount, a legacy system they're attached to, a reporting line that gives them influence.
When I see a transformation where nothing has been given up by the people commissioning it, I know the pain is going to land somewhere else — on the teams being asked to change without the resources, authority, or political cover to do so effectively.
Real transformation costs something at the top. If it hasn't, it's not transformation. It's reorganisation with better slide design.
None of this is a checklist. It's a diagnostic lens — a way of reading what's actually happening underneath the programme language and the status reporting. The organisations that pass all five tend to be the ones where something genuinely shifts. The ones that don't usually know it by month six, even if they don't say it out loud.
If you're in the middle of a transformation that feels stuck, the problem is rarely execution. It's almost always one of these five things. And the fix is rarely a new workstream.
Working through a transformation that isn't moving?
Infintrix works with organisations to diagnose why change programmes stall and build the governance conditions that make them move. If this resonates, let's have a conversation.