Most change programmes fail not because the strategy was wrong — but because the people weren't brought with it. The resistant director. The middle manager who has seen three of these before. The frontline team who have stopped believing. We understand every one of them. Not as stakeholder groups. As people with mortgages, career concerns, legitimate worries and very good reasons for their resistance.
We know the frameworks. ADKAR. Kotter's eight steps. Prosci. Lewin. We have applied all of them across government departments, FTSE businesses, defence programmes and fast-scaling startups. We are not dismissing them — they are useful maps.
But a map of the terrain is not the same as walking the terrain. And what we have learned — from years of being inside organisations at the moment of change — is that the frameworks do not tell you about the finance director who will quietly undermine the programme because it threatens her team's headcount. They do not tell you about the operations manager whose resistance is actually legitimate and whose concerns, if heard, would improve the design. They do not tell you about the person who needs to understand what this means for their mortgage before they can engage with what it means for the business.
We apply the principles of the frameworks — awareness, desire, knowledge, ability, reinforcement — but we apply them to actual human beings in actual situations. That is a different thing. And it is the thing that determines whether change actually lands.
Not because the strategy was wrong. Not because the technology failed. Because the people weren't brought with it. Because someone important didn't feel heard. Because the naysayer in the room was managed rather than understood. Because the pulse check came back amber and nobody changed course.
Because we treat the human element as the primary variable, not a workstream. Because we do not do pulse checks as a nice-to-have — we change course based on what they tell us. Because we understand politics, worry, career risk and uncertainty as forces in a system, and we work with them rather than around them.
"The adoption rate at go-live is the wrong metric. The right metric is whether the organisation is still using it, improving it and owning it twelve months later. That only happens if the people were genuinely brought with it."
The person who has decided this won't work before the first workshop. Who asks the hardest questions in every session. Who the programme board wants to manage out of the room.
We do not manage them. We listen to them — because they are often the person who understands the real obstacles better than anyone. When their concerns are heard and addressed, they become the programme's most credible advocate. When they are not, they become its most effective saboteur.
The people who are not resistant — they are uncertain. What does this mean for my role? My team? My working patterns? My career trajectory? They will not ask these questions in a town hall.
They will disengage quietly and adopt slowly. We create the conditions in which those questions get asked and answered — not in a survey, but in conversation. We understand that behind every change programme is a person with a mortgage, a family and a very understandable desire to know that they will be alright.
The senior leader who is publicly supportive and privately positioning. Who attends the steering group and misses the critical working session. Who has a legitimate interest in the outcome that has never been explicitly discussed.
We understand organisational politics not as a nuisance but as a force to be worked with. We identify the real interests at play, understand what each stakeholder needs to feel safe, and design an approach that gives them a reason to commit rather than comply.
We understand the rules — the formal ones and the informal ones. The policy that nobody reads but everyone hides behind. The process that exists to protect someone from a decision made in 2009. We navigate it rather than fight it, because fighting the rules is rarely the fastest path through them.
The person who is genuinely excited and wants to move faster than the programme allows. We find them early and use them well — not as cheerleaders, but as genuine agents of change who can speak to their peers in a language that we cannot.
Every one of these people is rational. They are responding to real information, real incentives and real uncertainty in a way that makes complete sense from where they are standing. Our job is not to overcome their resistance — it is to understand it well enough that we can address the thing underneath it.
Before we design anything, we understand who is in the system and what they actually think — not what they say in a stakeholder workshop, but what they believe when the consultants have left the room. We have been in those rooms. We know the difference.
Most programmes do engagement surveys and note the results in a RAG status. We treat them as live data that directly changes what we do next. If the worried majority are more worried than they were last month, we do not note it amber — we change the approach. This is the difference between monitoring change and managing it.
The most effective thing we do in a change programme is spend an hour with the person who has decided it won't work. Not to persuade them. To understand why. In almost every case, their objection contains information the programme needs — and addressing it directly turns the most visible doubter into the most credible advocate.
In government and regulated sectors especially, change happens within a framework of rules, policies and governance that cannot simply be redesigned out of the picture. We understand them. We know which ones are fixed and which ones are interpreted. We design change that works within the system rather than around it.
The day we go live is not the success metric. The question is whether the organisation is still using it, improving it and owning it twelve months later. That requires reinforcement that is designed in from the start — not added when adoption numbers disappoint.
"Change management frameworks are written for ideally rational humans in ideally functioning organisations. Real change happens to people with mortgages, career concerns, political allegiances and deeply understandable reasons for not wanting things to be different."
That is the gap between a change management plan and change that actually happens. We close it — because we have been in those rooms, and we know the difference between someone who is resistant and someone who has not yet been given a reason to trust.