News

Why Change Fails, And What To Do About It

change management agile

Most project plans end at go-live. The system is switched on, the new process is published, the training has been delivered and the project closure report goes to the steering group with a satisfying column of green. Yet anyone who has stayed close to a change programme for a few months afterwards knows that go-live is where the real test begins.

People start the new way of working on a Monday full of good intentions and by Thursday many of them have drifted back to the spreadsheet, the workaround or the habit they have relied on for years.

We are often told that 70 per cent of change programmes fail. It is worth knowing that when Mark Hughes of Brighton Business School went looking for the evidence behind that figure, publishing his findings in the Journal of Change Management in 2011, he found no valid research to support it. The statistic is shaky, but the experience behind it is real enough, and most project managers will recognise the pattern of a change that was delivered on time and on budget and then never quite took hold.

Delivery is not adoption

The reason, in my experience, is that organisations plan the change in great detail and plan the days after it hardly at all. A project is built to deliver an output, while change only happens when hundreds of individuals each alter what they do at their desks, in their meetings and on their calls. Those are two very different jobs, and the second one rarely has a workstream, a budget or an owner once the project team has moved on to the next thing.

In my book After Monday I set out a ten stage pathway from intention to lasting change, and the third stage, False Hope, describes this moment well. It is the trap of mistaking understanding for progress. Everyone has attended the briefing, everyone can explain why the new way is better, and so it feels as though the change has happened. Knowing what to do and doing it consistently when the pressure is on are separate things, and the gap between them is almost always about discomfort rather than ignorance.

Four reasons change stalls

The first is that the plan sits at the level of the organisation rather than the person. A roadmap tells you when the system goes live, but it says nothing about what a team leader will do differently at nine o’clock on a Tuesday. The Plan stage of the pathway is about making the change specific enough for an individual to act on, and Everyday Action is about the small, unglamorous repetitions that turn it into habit.

The second is that we avoid The Truth. Some years ago I took part in a Tough Mudder with thirty colleagues, and on the final sprint up a ramp I was convinced I had found my inner Usain Bolt. Then I watched the video and saw that I was barely jogging. Change programmes do this constantly. The status report says green because the milestones were met, while out in the business people are quietly running the old process alongside the new one. If nobody goes and looks at what is really happening, the problem stays invisible until the benefits fail to arrive.

The third is that new behaviour gets worse before it gets better. Trying something unfamiliar feels clunky, productivity dips and the old way starts to look attractive again. What people are experiencing is transition rather than failure, but unless someone says so they tend to give up just before the new approach would have started to feel normal. This is why The Pivot and Go Again matter so much, adjusting based on what the feedback shows and then going round the loop again, many more times than anyone planned for.

The fourth is that people are left to do it alone. Sponsors are highly visible at launch and often much harder to find three months later. Yet Not Alone, having someone who notices the effort, asks how it is going and encourages people when it would be easier to stop, is one of the two stages I regard as most important in the whole pathway.

What to do about it

For project managers the practical shift is to treat adoption as part of the deliverable rather than something that happens after closure. Plan the ninety days after go-live with the same care as the build, and translate the change into two or three specific behaviours for each role so people know exactly what doing it looks like. Go and see what is really happening in the business rather than relying on milestone reports, and warn people in advance that the early weeks will feel harder, so the dip is expected rather than alarming. Finally, keep sponsors and line managers visibly involved well beyond launch, because people persist when someone notices whether they did.

Go-live is where a change is introduced, but it is in the ordinary weeks that follow that it either sticks or fades away.

Jeremy Campbell, CEO of Black Isle Group, has spent 45 years observing how people and businesses change, and writes about it in his book, After Monday: A Simple Pathway from Intention to Lasting Change (out now)

Jeremy Campbell
Related News
Related sized article featured image

Council recognised for transforming its homelessness service as temporary accommodation costs surge and demand exceeds 1,000 applications a month.

News Team
Related sized article featured image

HSBC survey of 10,000 business leaders finds rising costs are forcing companies to rethink supply chains, improve efficiency and accelerate AI adop...

News Team