Change Management: What Actually Helps Organisational Change Stick
August 2, 2026 · Professional Development · 10 min read
Organisational change is difficult, but not because there is a universal law that most change initiatives fail. The widely repeated claim that 70% of organisational change initiatives fail is not supported by reliable empirical evidence. A peer-reviewed review by Mark Hughes traced multiple versions of the claim and concluded that there was no valid and reliable evidence for a fixed 70% failure rate.
That does not mean change is easy. It means organisations should focus less on dramatic failure statistics and more on the conditions that make implementation more or less likely to work: readiness, leadership engagement, employee involvement, communication, resources, manager support, practice and measurement.
What is change management?
Change management is the structured work of helping an organisation and its people move from a current way of working to a desired future state. The technical project and the people side of change are connected. A new system, policy, operating model or organisational structure can be technically sound and still underperform if people do not understand it, cannot use it, do not have the resources to adopt it or do not see leaders behaving consistently with the change.
Effective change management therefore covers more than communication. It includes diagnosing readiness, clarifying outcomes, identifying affected groups, preparing leaders and managers, building capability, creating opportunities for participation, managing barriers to adoption and measuring whether the new behaviour or process is actually taking hold.
The 70% failure statistic is not a reliable benchmark
The famous 70% figure appears in influential management writing, including a 2000 Harvard Business Review article. However, the assertion was not accompanied by a study, sample or agreed definition of failure. Hughes’ 2011 review in the Journal of Change Management examined several published versions of the statistic and found no valid and reliable empirical evidence supporting an inherent 70% organisational-change failure rate.
This matters because change outcomes are rarely binary. A programme may deliver some objectives but not others, reach one business unit before another, exceed its original timeline while still producing value, or achieve technical deployment without full behavioural adoption. Treating all of those outcomes as simply success or failure hides the information leaders actually need.
What the evidence says matters for organisational change
1. Readiness is specific to the change
Organisational readiness is not simply whether employees have a positive attitude. Research on readiness for change treats it as a combination of psychological and behavioural preparedness. A systematic review of readiness assessments found that the factors most often measured included implementation readiness, communication and networks, implementation climate, organisational structure and culture.
For practitioners, the implication is straightforward: do not ask only whether people are ‘ready for change’ in general. Ask whether they understand this change, believe it is workable, have the resources and knowledge needed to implement it, and see the surrounding organisation supporting the new way of working.
Source: Systematic review of organisational readiness for change assessments
2. Leadership sponsorship has to be visible and sustained
Senior sponsorship is more than approving a project at the beginning. Prosci’s long-running practitioner research consistently identifies active and visible sponsorship as a major contributor to change success. Effective sponsors remain involved, build support among other leaders and communicate why the change matters.
A common failure mode is symbolic sponsorship: a senior leader’s name appears on the project, but employees rarely see that leader explain priorities, resolve conflicts, allocate resources or reinforce the new behaviour. When leaders continue rewarding the old way of working, employees reasonably conclude that the change is optional.
Source: Prosci research on effective sponsorship
3. Employee involvement improves ownership and readiness
Participation matters because employees often understand operational constraints that are invisible at programme level. Research on employee engagement, ownership and participation during organisational change has found positive relationships between participation in decision-making and readiness-related outcomes.
Participation does not mean every employee decides the final direction. It means affected employees have meaningful opportunities to surface risks, test assumptions, improve workflows and understand how decisions were made. Consultation that cannot influence anything quickly becomes performative and may reduce trust rather than build it.
Source: Research on employee engagement, ownership, participation and change readiness
4. Communication should answer operational questions, not just promote the change
Change communication is strongest when it helps people act. Employees need to know what is changing, why it is changing, what is not changing, when the change affects them, what they need to do differently, where they can get help and how feedback or problems will be handled.
Repeated slogans about transformation are not a substitute for role-specific information. A finance employee, line manager, customer-service representative and IT administrator may all need different information about the same change. Communication should therefore be segmented by audience and linked to actual decisions, tasks and milestones.
5. Managers are the local translation layer
Employees often experience organisational change through their immediate manager. Managers explain priorities, allocate work, answer questions, identify resistance, notice capability gaps and decide whether new behaviours are reinforced in daily operations.
That makes manager preparation a design requirement rather than an optional communication step. Managers need enough notice, context and practical guidance to answer predictable questions. They also need a route for escalating issues they cannot resolve locally.
6. Capability and resources matter as much as willingness
Resistance is sometimes blamed on attitude when the real barrier is capability. People may support a change and still be unable to implement it because training is inadequate, systems are not ready, workloads leave no time for practice, policies conflict with the new process or local teams lack authority to make required decisions.
Before labelling behaviour as resistance, distinguish among four different problems: people do not understand the change, do not believe it will work, do not know how to perform the new behaviour, or cannot perform it because the environment makes it difficult. Each problem requires a different intervention.
7. Reinforcement determines whether adoption lasts
A launch date is not the end of a change programme. Teams often return to familiar routines when workload rises or leadership attention moves elsewhere. Reinforcement can include updated performance measures, manager follow-up, process documentation, coaching, system prompts, peer support and removal of old processes that compete with the new one.
Where possible, retire the old pathway rather than asking employees to choose indefinitely between old and new systems. Parallel processes may be necessary during transition, but leaving both in place permanently can undermine adoption.
How to diagnose change readiness before implementation
A practical readiness assessment should examine several dimensions instead of producing one generic score.
- Purpose: Do affected groups understand the problem the change is meant to solve?
- Leadership: Are sponsors aligned and visibly committed?
- Manager readiness: Can managers explain the change and support their teams?
- Capability: Do people have the knowledge and skills required?
- Resources: Are time, systems, staffing and budget adequate?
- Process fit: Does the new approach fit other policies, incentives and workflows?
- Trust: Do employees believe concerns will be heard and handled fairly?
- Measurement: Is there a clear way to distinguish deployment from actual adoption?
Change frameworks are planning tools, not guarantees
Kotter’s eight-step model, Prosci’s ADKAR model, Lewin’s change model and other frameworks can help teams organise their thinking. None should be treated as a universal formula that guarantees success.
Different changes create different problems. A new HR system may depend heavily on workflow redesign and user capability. A merger may create identity, trust and role-clarity issues. A regulatory change may have a fixed compliance deadline. A culture initiative may require sustained reinforcement over years. The framework should serve the change, not become the change.
Measuring change: move beyond attendance and launch dates
Training completion, emails sent and launch milestones show that activity occurred. They do not prove adoption.
A stronger measurement plan separates several levels:
- Awareness: Do affected employees understand the change and its purpose?
- Capability: Can they perform the new tasks or behaviours?
- Adoption: Are they actually using the new process, system or behaviour?
- Proficiency: How well are they performing after adoption?
- Operational outcome: Are the intended process, customer, risk, quality or performance measures improving?
The exact measures should match the initiative. A system implementation can use login, workflow and error data. A management-behaviour change may require employee feedback, observed behaviours and team outcomes. A policy change can track compliance, exceptions and processing time.
Change management in multicultural and multi-location organisations
Organisations operating across the GCC, Africa and Asia often implement change across teams with different languages, organisational histories, professional norms and levels of authority. That increases the importance of local interpretation.
Central teams should define the non-negotiable outcome while allowing local teams to identify practical barriers and communication needs. Translation should focus on meaning, not only language. Managers may also need guidance on how to create space for questions in teams where employees are reluctant to challenge senior decisions openly.
This does not require assuming that everyone in a country or culture behaves the same way. It requires recognising that the same corporate message may be interpreted differently across teams and testing whether people actually understand what they are being asked to do.
A practical change-management sequence
- Define the outcome. Describe what will be observably different when the change is working.
- Map affected groups. Identify who must adopt, support, approve or enable the change.
- Assess readiness and barriers. Examine leadership, capability, resources, process fit and trust.
- Engage sponsors and managers. Clarify their responsibilities before broad communication begins.
- Involve employees in design and testing. Use their operational knowledge to improve implementation.
- Build capability. Provide training, practice, job aids and support tied to real tasks.
- Communicate by audience. Answer role-specific questions instead of repeating one generic message.
- Measure adoption and proficiency. Track whether the new behaviour is happening, not only whether it was announced.
- Reinforce and adjust. Remove old processes, address barriers and continue support after launch.
Frequently asked questions
Do 70% of change initiatives fail?
There is no reliable empirical basis for a universal 70% failure rate. A peer-reviewed review found that the widely repeated statistic was not supported by valid and reliable evidence. Change outcomes also depend heavily on how success and failure are defined.
What is the most important factor in change management?
No single factor guarantees success. Evidence and practitioner research repeatedly point to a combination of leadership engagement, organisational readiness, communication, employee involvement, adequate resources, manager support and reinforcement.
How should resistance to change be managed?
Start by diagnosing the reason. Apparent resistance can reflect lack of understanding, disagreement with the rationale, low trust, insufficient skills, workload pressure or practical barriers. Addressing the actual cause is more useful than treating resistance as a personality problem.
How do you know whether a change has been adopted?
Measure the behaviour or process that should be different after implementation. Depending on the initiative, this might be system usage, workflow completion, error rates, policy compliance, observed management behaviour, customer outcomes or employee feedback. Completion of training alone is not evidence of adoption.
Build change capability around real organisational work
MATSH provides professional learning in leadership, communication, management and organisational capability. Change-management development is most useful when participants work on real implementation challenges and leave with practical actions for sponsors, managers and employees.
Explore MATSH change-management training or review our evidence-based guide to leadership development programmes.
Sources
- Hughes, M. (2011), Journal of Change Management – Do 70 Per Cent of All Organizational Change Initiatives Really Fail?
- Unpacking organizational readiness for change: systematic review and content analysis
- Research on employee engagement, ownership, participation and change readiness
- Prosci – research on active and visible sponsorship
Need In-House Training?
We run all our courses as private programmes for organisations across the GCC and Africa.
Request In-House →