Every year, organisations invest millions in transformation programmes. They hire consultants, select frameworks, announce the change at an all-hands, and set up steering committees. Six months later, half of them are wondering why nothing has fundamentally shifted. A year later, the word "transformation" has become quietly embarrassing. People say it with a slight wince, usually followed by "we tried that."
I have been in those rooms. I have sat across the table from leadership teams who genuinely believed they were ready, who had done the workshops and signed off the roadmap and commissioned the culture survey. And I have watched, sometimes within weeks, as the same patterns reasserted themselves. The governance that was supposed to change did not change. The decisions that were supposed to happen faster did not happen faster. The people who were supposed to speak up stayed quiet.
Having led transformation across defence, financial services, healthcare, and enterprise software for over twenty years, the diagnosis is almost always the same. The programme did not fail because the methodology was wrong. It failed because the organisation was never actually ready, and nobody said so.
"Readiness is not about appetite. Every leadership team says they want to transform. Readiness is about whether the organisation has the capacity, the clarity, and the psychological safety to do what transformation actually requires."
What transformation actually requires
Before I talk about readiness, it is worth being precise about what transformation actually demands of an organisation. Not what it says on the programme initiation document. What it actually requires in practice.
Transformation requires people to tell the truth about what is not working. That sounds simple. In practice, in most organisations, it is the hardest thing to do. People have careers invested in the current state. They have built teams, processes, and reputations around the way things work now. Asking them to acknowledge that the way things work now is the problem is asking them to implicate themselves.
Transformation requires decisions to be made under uncertainty. Most organisations are extraordinarily good at deferring decisions until there is more information. Transformation moves faster than certainty. If your leadership team cannot commit to a direction without a 90-page business case and three rounds of governance approval, the programme will stall at every turn.
Transformation requires tolerating a period where things feel worse before they get better. This is perhaps the most underestimated demand of all. The old ways stop working before the new ways are properly embedded. Productivity dips. Confusion rises. People question whether the whole thing was a mistake. Leaders who have not been prepared for this will pull the plug — often exactly when they should be doubling down.
The three questions no transformation process ever asks
In my experience, most transformation programmes begin by selecting a framework and commissioning a current-state assessment. What they almost never do is ask the three questions that actually determine whether the programme will succeed.
What decisions need to be made differently?
Not what processes need to change. Not what tools need to be implemented. What decisions. Who is making them, how quickly, with what information, and with what authority. In most organisations, the decision-making architecture is the invisible constraint that no framework ever touches — because frameworks describe what should happen, not who has the power to make it happen.
I have seen organisations implement quarterly planning beautifully. The cadence, the ceremonies, the wall coisation — and achieve nothing, because the people in the planning events did not have the authority to commit to anything. Every commitment went back to a steering committee that met once a month and operated on a different rhythm entirely.
What behaviours need to change?
Not what the organisation says it values. What it actually rewards. In most organisations, there is a significant gap between the behaviours that are espoused in the transformation vision and the behaviours that actually get people promoted, recognised, and protected when things go wrong.
If you tell teams to be transparent about risks and then punish the people who surface bad news, you will get a culture of performance rather than a culture of delivery. People will report green when things are amber and amber when things are red. The transformation programme will proceed on false data until it cannot anymore.
Real transformation requires leaders to visibly model the behaviours they are asking for. That means admitting uncertainty. It means changing a decision when new information arrives rather than defending the original position. It means celebrating the team that flagged a problem early rather than the team that kept quiet until it was too late.
What does the organisation need to stop doing?
This is the question that almost never gets asked, and it is the most important of the three. Every transformation programme adds new things — new processes, new ceremonies, new tools, new governance structures. Very few take anything away. The result is that people end up doing the old way and the new way simultaneously, which means they do neither well, and they resent the transformation for the additional burden it has placed on them.
The most effective transformations I have been part of have been as much about subtraction as addition. What meetings can we stop having? What reports can we stop producing? What approval steps can we remove? What work is being done that no one actually reads or uses? Freeing up capacity is not a nice-to-have — it is a prerequisite for sustainable change.
What readiness actually looks like
Readiness is not a checklist. It is not a maturity model score or a cultural survey result. It is a set of conditions that make transformation survivable — and I use that word deliberately, because transformation, done properly, is uncomfortable.
- Leadership alignment that goes beyond the boardroom. The executive team agrees on the direction, yes — but middle management, who actually run the organisation day to day, understand what is being asked of them and why.
- Honest diagnosis of the current state. Not a sanitised version. The real constraints, the real blockers, the real reasons things work the way they do. Without this, you are solving for the symptom rather than the cause.
- Capacity to absorb change. If the organisation is already at maximum operational load, adding a transformation programme on top is a recipe for exhaustion and failure. Something has to give before the transformation begins.
- Psychological safety to surface problems. People at every level need to feel that raising a concern will be welcomed rather than penalised. This is cultural, not procedural — and it cannot be declared into existence.
- A sponsor with real authority and genuine commitment. Not a senior name on a steering committee who attends one in three meetings. A sponsor who removes blockers, makes decisions, and backs the programme when it gets difficult.
What to do if the organisation is not ready
Here is the hard part. Sometimes, when you ask the right questions, the honest answer is that the organisation is not ready. The leadership team is not aligned. The capacity is not there. The culture will not support what the transformation requires.
Most consultants and most transformation leaders do not say this out loud. The engagement has been sold, the contract has been signed, the announcement has been made. Saying "actually, we are not ready" feels like failure. It feels like the wrong answer.
In my experience, it is the most valuable answer you can give.
Because the alternative — proceeding with a transformation programme into an organisation that is not ready — is not a neutral act. It does not simply fail quietly. It damages things. It burns out the people who tried to make it work. It creates cynicism that makes the next attempt harder. It confirms the belief, held by the sceptics who were there from the start, that "this is just another change programme that will pass."
"The most valuable thing a transformation leader can sometimes do is tell an organisation what it needs to hear rather than what it wants to hear — and then help it become ready."
That might mean six months of focused leadership development before the transformation begins. It might mean a smaller, bounded pilot that builds the conditions for something larger. It might mean a frank conversation with the board about what this will actually require from them — not in terms of budget, but in terms of their own behaviour and commitment.
The EWoW approach to readiness
When I work with organisations through my Evolved Ways of Working (EWoW) methodology, I spend significant time at the outset on what I call the readiness conversation. Not an assessment that produces a traffic-light score. A genuine, often uncomfortable conversation about what is actually going on, what the organisation is actually capable of right now, and what conditions need to exist for the transformation to succeed.
EWoW is not a framework imposed from outside. It is an approach that evolves the organisation from within — which means it has to start where the organisation actually is, not where the programme plan assumes it is. That distinction changes everything.
The result is transformation that takes longer to start and less time to fail. Organisations that go through this process end up with change that is embedded, sustained, and owned internally — not dependent on the consultancy continuing to prop it up.
A final thought
The transformation industry has a vested interest in the idea that failure is a methodology problem. If the programme failed, it is because you chose the wrong framework, or did not implement it correctly, or did not have the right tools. Buy the next version, hire the next consultant, try again.
In most cases, that is not true. In most cases, the programme failed because the organisation was not ready, and no one asked whether it was before they started.
Ask the question. Do the work to get ready. Then transform.
That is how it sticks.
Working through a transformation challenge?
If this resonates with something your organisation is experiencing, I am happy to have a direct conversation about what readiness looks like in your context.
Get in touch
20+ years delivering transformation across defence, NHS, financial services and enterprise. Creator of EWoW — Evolved Ways of Working. Available for Head of Transformation, Director of Transformation and senior consulting engagements across the UK.