Why This Level Matters
You are about to introduce a change, such as a new system, a new process or a new team structure. Most managers put their effort into the solution: the software, the process map, the organisation chart. This course is about the other half of the work, which is getting people to actually change how they work. This first level explains why change efforts so often fall short, so you can recognise the warning signs in your own project.
Delivered Is Not the Same as Adopted
The most important distinction in this course is between two kinds of success:
- Delivery (technical success): the solution is built, tested and switched on. The project closes on time and on budget.
- Adoption (people success): people use the solution properly, keep using it, and the expected benefits appear.
A project can achieve delivery and fail at adoption. The benefits in a business case, such as faster processing, better data or lower costs, only appear when people change their daily behaviour.
Worked example: a CRM roll-out
A sales team of 40 gets a new customer relationship management (CRM) system. The project team:
- Configures the system and migrates the data.
- Runs one 90-minute training session the week before go-live.
- Switches off the old database on schedule.
The project is reported as a success. Three months later:
- Half the sales staff still keep their pipeline in personal spreadsheets.
- Records in the CRM are incomplete, so the sales forecast is unreliable.
- Managers stopped checking CRM data after the first month, so staff conclude it doesn't matter.
Nothing was wrong with the software. The change failed on the people side: no visible leadership, little explanation of why, training that came too early and was too thin, and no follow-up.
What to do: for your own change, write one sentence describing what 'adopted' will look like in observable behaviour (for example, 'All new opportunities are logged in the CRM within 24 hours').
Common People-Side Causes of Failure
Researchers and practitioners keep reporting the same causes. Use this as a checklist:
- Weak or absent sponsorship. A senior leader approves the change and then disappears. Prosci's Best Practices in Change Management research has ranked active and visible sponsorship as the top contributor to success in every edition of its benchmarking studies since 1998.
- No clear case for change. People are told what is changing but not why, so it looks like change for its own sake.
- Poor or one-way communication. One announcement email, jargon, and no chance to ask questions. In his 1995 Harvard Business Review article 'Leading Change: Why Transformation Efforts Fail', John Kotter listed under-communicating the vision among the common errors.
- Ignored resistance and concerns. Objections are treated as obstruction rather than as information. Real problems, such as a workflow the new system doesn't support, stay hidden.
- Impacts not understood. Nobody worked out which groups are affected and how. One team loses half a day a week and nobody planned for it.
- Inadequate training and support. One-off training, delivered too early, with no help available after go-live.
- Declaring victory too soon. The project team moves on at go-live, and old habits return. Kotter also named this error.
- Change overload. The change lands on people already coping with several others, and it gets the least attention.
What to do: score your change against each item above as red, amber or green.
Treat Failure Statistics with Caution
You will often hear that '70% of change initiatives fail'. Be careful before repeating it.
- Origin: in Reengineering the Corporation (1993), Michael Hammer and James Champy gave what they called an 'unscientific estimate' that 50 to 70% of organisations attempting reengineering did not achieve the dramatic results they intended. Hammer later said the figure had been distorted, and that reengineering has no built-in success or failure rate.
- Repetition: Michael Beer and Nitin Nohria's 2000 Harvard Business Review article 'Cracking the Code of Change' stated that about 70% of change initiatives fail, without empirical evidence to support the figure.
- Challenge: Mark Hughes reviewed five published sources of the 70% claim in the Journal of Change Management (2011). He found no valid and reliable empirical evidence for it.
- Survey data: McKinsey's global surveys report that fewer than one-third of respondents say their transformation succeeded in improving performance and sustaining it. This is useful, but it is self-reported opinion, not measured outcomes.
Why the figures are disputed:
- 'Failure' is rarely defined. Late? Over budget? Benefits missed? Abandoned?
- Different kinds of change are lumped together.
- Many figures come from surveys or consultancy reports, not independent research.
What to do: when you make a case to your sponsor, don't rely on a headline rate. Use specific risks from your own project and evidence from earlier changes in your organisation.
Run a Quick Failure Pre-Mortem
Use this short procedure before your change starts:
- Define adoption. Write down the observable behaviours that will show the change has been adopted.
- Imagine failure. Assume it is six months after go-live and the change has not been adopted. Ask your team: 'Why did it fail?'
- Match the reasons to the checklist. Sort each reason under the causes listed above.
- Rate and act. Rate each cause by likelihood and impact, then name one action and one owner for each high-rated cause.
Later levels give you the tools for these actions.
Key Takeaways
- A delivered solution is not an adopted change. Benefits depend on people changing how they work.
- Common people-side causes include weak sponsorship, no clear case for change, poor communication, ignored resistance, unassessed impacts, thin training and support, declaring victory too soon, and change overload.
- Sponsorship is consistently reported as the single biggest success factor.
- The '70% fail' figure traces back to an admitted 'unscientific estimate' and lacks reliable empirical support. Use it with caution, if at all.
- Define adoption in observable terms and run a pre-mortem before you begin.