Most change programs do not fail because the strategy was wrong. They fail because the organisation could not absorb the change at the pace the plan demanded. That is why choosing from the best change management approaches is not a theory exercise. It is a delivery decision that affects adoption, risk, cost, timelines and leadership credibility.
If you are leading a system rollout, operating model shift, compliance uplift or business transformation, the right approach is the one that fits your environment - not the one with the cleanest diagram. A mutual bank managing regulatory change has different needs from a community housing provider replacing core systems. A construction business integrating new governance processes faces a different stakeholder profile from a healthcare provider introducing digital workflows. Context matters.
What makes a change management approach effective?
The best change management approaches do three things well. They create clarity about what is changing and why. They help leaders and frontline teams move at a realistic pace. And they build enough structure around the work that adoption does not get left to chance.
That sounds simple, but most organisations undercook at least one of those areas. They communicate heavily but do not shift behaviour. Or they train people well but ignore sponsor alignment. Or they design a strong change plan that collapses when delivery pressures hit. Effective change management is not a communications stream bolted onto a project. It is part of how the work is governed and executed.
1. ADKAR for individual adoption
ADKAR remains one of the most practical frameworks because it focuses on the individual journey through change - awareness, desire, knowledge, ability and reinforcement. It is especially useful when the business case is clear, the change has a defined end state, and success depends on people doing something differently day to day.
This approach works well for technology deployments, process changes and role-based operational shifts. It gives leaders and project teams a simple way to test where adoption is breaking down. If people know what is changing but still are not engaging, the problem is not communication alone. It may be desire. If they support the change but still cannot perform in the new environment, the issue is ability, training or process design.
The trade-off is that ADKAR can become too individualised if used in isolation. It does not replace stakeholder strategy, governance or organisational design. It is strongest when paired with solid program controls and active sponsorship.
2. Kotter’s 8-step model for large-scale transformation
Kotter’s model is useful when the organisation needs broad mobilisation, not just user adoption. Its strength lies in building urgency, aligning leadership, creating visible wins and sustaining momentum over time. For major transformations - mergers, enterprise technology change, cultural resets or multi-year business reform - that sequence can be valuable.
Where Kotter helps is in reminding executive teams that change does not move because a steering committee approved a plan. It moves when leaders are visibly aligned, middle management is engaged and the organisation sees early proof that the effort is working.
The limitation is speed. In fast-moving environments, a strict step-by-step reading of Kotter can feel too linear. Real projects often require overlapping stages, rapid decision-making and ongoing reprioritisation. Used rigidly, it can slow execution. Used pragmatically, it helps leaders avoid the common mistake of launching change before the organisation is ready.
3. Lewin’s change model for simpler environments
Lewin’s unfreeze-change-refreeze model is often criticised for being too basic, but that simplicity is exactly why it still has value. When the change is relatively contained and the organisation needs a straightforward structure, this model can work well.
It is particularly useful for policy, compliance or procedural shifts where the current state needs to be clearly disrupted, a new way of working introduced, and then embedded through controls, reporting and leadership expectations. In regulated sectors, that final stabilisation step matters.
The challenge is that many organisations do not operate in stable conditions for long enough to truly refreeze anything. If your business is going through continuous transformation, the model can feel dated. It suits contained change better than ongoing evolution.
4. Agile change management for evolving programs
Not all change can be mapped neatly at the start. In digital transformation, product-led delivery and complex operational reform, the solution often evolves as the program progresses. Agile change management is better suited to that reality.
Rather than waiting for a perfect end-state design, this approach builds change activity iteratively. Stakeholder feedback is gathered early. Messaging is adjusted as the solution develops. Training is released in waves. Resistance is identified sooner because users are engaged throughout delivery rather than only at go-live.
This approach is well suited to organisations that already work in agile ways or need to respond quickly to changing requirements. But it has a weakness too. Without strong governance, agile change can become vague. Teams talk about iterating, but no one owns adoption outcomes, decision rights or cutover readiness. Agile methods do not remove the need for discipline. They increase it.
5. Prosci-style enterprise change for repeatability
Many organisations are not looking for a one-off framework. They need a repeatable method that can be applied across multiple programs, portfolios or business units. A structured enterprise approach, often influenced by Prosci-style methods, helps create consistency across stakeholder planning, sponsor activity, communications, training and readiness.
This is useful when change is happening across several initiatives at once and leadership needs visibility over cumulative impact. It supports better sequencing, clearer reporting and stronger governance, especially in organisations where delivery maturity varies between teams.
The risk is bureaucracy. If the framework becomes too process-heavy, change teams end up producing artefacts no one uses. The method should support delivery, not become a reporting exercise. Good change management is measurable and structured, but it still needs to feel practical to the people doing the work.
6. Nudge-based behavioural change for culture and habits
Some changes fail because organisations assume logic is enough. It rarely is. Behavioural approaches draw on habit formation, incentives, social proof and environmental design to shift how people act in practice.
This is particularly effective for culture change, safety, compliance behaviours, customer service standards and process adherence. If the goal is not just awareness but repeated behaviour at scale, behavioural design can be more useful than broad communications campaigns.
Still, this approach should not be oversold. Behavioural nudges can improve adoption, but they cannot compensate for poor leadership alignment, broken systems or unrealistic workloads. People resist change for rational reasons too. If the operating model makes the new behaviour harder than the old one, no poster campaign will fix it.
7. Hybrid models for real-world delivery
In practice, many of the best change management approaches are hybrids. A major transformation might use Kotter to mobilise leadership, ADKAR to support impacted teams and agile methods to manage evolving solution design. That is not a compromise. It is often the smartest way to match method to reality.
Experienced delivery leaders rarely ask, which framework should we follow exactly? They ask, what will help this organisation move? That shift in thinking matters. Frameworks are tools. They are not the outcome.
How to choose the right approach
Start with the shape of the change. If the solution is well defined and success depends on individual adoption, ADKAR is often a strong fit. If the business needs enterprise-wide mobilisation and strong executive sponsorship, Kotter may be more useful. If the change is contained and procedural, Lewin may be enough. If the program is iterative and solution design is still moving, agile change methods will likely serve you better.
Then look at delivery maturity. A framework that works in a mature PMO environment may fail in a lean organisation with limited internal capacity. The same applies to sponsor capability. Some models rely heavily on active executive leadership. If that is weak, the method may need to be adapted and supported more closely.
Finally, assess change saturation. A good framework can still fail if the organisation is already overloaded. This is where experienced program and project leadership makes the difference. Change management cannot sit in a separate lane from delivery planning, risk management and operational readiness. It needs to be integrated from the start.
Why approach alone is not enough
Organisations often ask for a framework when the real issue is execution. They have a change plan, but no sponsor follow-through. They have stakeholder mapping, but weak governance. They have communications drafted, but no clear decision-making path. The model is not the problem.
What matters is whether the chosen approach is translated into action, measured consistently and adjusted when reality changes. That takes more than templates. It takes embedded leadership, clear accountability and the discipline to keep adoption on the agenda when timelines tighten.
At JJPH, we see this regularly across technology, compliance, infrastructure and transformation programs. The approach matters. But the organisations that get results are the ones that connect change management to delivery management rather than treating it as a parallel workstream.
The best choice is rarely the most academic one. It is the one your leaders will use, your teams can absorb and your program can govern properly. If your organisation is carrying real delivery risk, that is the standard worth applying.
