Every enterprise IT programme has a change management plan. Most of them don't work. Not because the people writing them don't understand change management, but because the plan is treated as a deliverable rather than a discipline.
Change management gets scoped, budgeted, and then delivered in isolation from the rest of the programme. A communications lead sends updates. A training team builds e-learning modules. A stakeholder map gets produced and filed. And then, at go-live, the organisation discovers that none of it was enough.
The problem isn't that organisations don't invest in change management. It's that they invest in the wrong things at the wrong time.
Where Change Management Actually Breaks Down
The failure modes are consistent across industries and geographies. I've seen the same patterns in financial services programmes in London and government transformation programmes in the Gulf.
Change management starts too late. It's brought in after the solution has been designed, when the decisions that most affect people have already been made. By the time the change team arrives, resistance is already baked in.
It's separated from programme governance. The change lead reports to a communications director, not the programme director. Change risks don't appear on the programme risk register. Change readiness isn't a go-live criterion.
The focus is on communication, not commitment. Telling people about a change is not the same as securing their commitment to it. Newsletters and town halls inform. They don't build the capability or willingness to work differently.
Middle management is ignored. Senior leaders endorse the change. Frontline staff are trained. Middle managers, who are responsible for embedding new ways of working, are left to figure it out themselves. They often revert to what they know.
Success is measured at go-live, not at adoption. The change management plan ends when the system goes live. But that's when the real change begins. Post-go-live adoption, capability building, and behaviour change take months, not weeks.
Research from McKinsey found that 70% of transformation programmes that fail do so because of people and organisational factors, not technical ones. Change management isn't a soft discipline. It's the primary risk on most enterprise IT programmes.
What Effective Change Management Looks Like
Effective change management isn't a separate workstream. It's integrated into every aspect of programme delivery from day one.
| Principle | What It Means in Practice |
|---|---|
| Start at design | Change leads involved in solution design, not just implementation |
| Integrate with governance | Change readiness on every steering agenda; adoption as a go-live gate |
| Build middle management capability | Dedicated support for managers to lead their teams through change |
| Measure adoption, not activity | Track system usage, process compliance, and behaviour change post go-live |
| Plan for 12 months post go-live | Change management budget and resource extends well beyond implementation |
The most effective change management intervention I've seen isn't a framework or a methodology. It's a conversation with the people most affected by the change, early enough that their input can actually shape the solution.
When people feel heard in the design process, they're significantly more likely to support the outcome. When they're told about a decision that's already been made, they resist it. This isn't psychology; it's programme management.
If your change management plan is a Gantt chart of communications activities, it's not a change management plan. It's a communications plan.
Sustainable change requires leadership commitment, middle management capability, and a programme structure that treats adoption as an outcome, not an afterthought. If your programme is struggling with adoption or resistance, we can help diagnose what's not working and restructure the approach. Book a 30-minute discovery call.