Guide · Organizational change
Why change management fails in organizations
Roughly seventy percent of corporate change programmes fail to deliver what they set out to. The number has barely moved in three decades, despite better frameworks, better tooling and better trained leaders. The reason isn't a shortage of models. It's that most models treat change as a project to be managed rather than a set of human behaviours to be understood.
The seven reasons change management fails
1. The initiative is framed as a process, not a behaviour shift
Traditional change management (Kotter, ADKAR, Lewin) gives you a sequence to run. It doesn't tell you what to do when someone in the middle of that sequence quietly disengages. Programmes measure milestones. Humans experience momentum, doubt and fatigue. The two don't line up.
2. Leaders confuse announcing with landing
A town hall, a deck and a Q&A is not adoption. It's a launch. Most change programmes over-invest in the first two weeks and under-invest in the next twelve months, which is precisely when False Hope arrives and people start reverting.
3. Middle managers are asked to sell a change they didn't help design
The layer that actually delivers the change is usually the last one consulted. They become messengers for a story they don't fully believe, which their teams read instantly. Consistency collapses at the layer where it matters most.
4. There's no diagnostic for where people get stuck
Two people can fall off the same change at completely different points. One never starts. One starts brilliantly and stops asking for help. One sustains for a month then loses interest. Treating them with the same intervention is why one-size-fits-all rollouts underperform.
5. Consistency is treated as a personality trait, not a system
Organisations reward the visible parts of change: kickoffs, dashboards, wins. They rarely design for the boring middle, where the actual work happens. Without a rhythm that survives quiet weeks, the change dies quietly.
6. False Hope is mistaken for success
Early enthusiasm gets read as adoption. It isn't. It's the honeymoon. If leaders declare victory in week three, the programme has no plan for week thirteen, which is when most people were going to need it.
7. The programme ends before the behaviour is embedded
Change is treated as something to complete. Behaviour is something to sustain. When the programme's budget ends, the reinforcement ends with it, and the organisation drifts back to whatever was easier before.
Traditional frameworks vs. a human-centric model
Kotter's eight steps, ADKAR and Lewin's unfreeze–change–refreeze all describe what an organisation should do. They say very little about what the person on the receiving end actually experiences. The After Monday model starts on the other side of that equation: it maps the points at which real people stall, and gives leaders a way to see, name and support those moments before they compound.
The shift is small but decisive. Instead of running everyone through the same playbook, you diagnose where each person tends to fall down (starting, sustaining, asking for help, recovering from a setback) and design the support around that. It's the difference between a programme that looks good on a slide and one that's still running a year later.
See where your people actually get stuck
The Change Profile Diagnostic is a five-minute behavioural assessment that shows which stage of the change journey a person struggles with most. It's the same diagnostic Jeremy uses inside keynotes and leadership programmes with organisations navigating real change.