Change Management Models: A Guide for Leaders

A change management model should help leaders make better choices, not add another layer of jargon. The right model gives people a shared way to name the work, prepare for it, and keep it moving when the first plan meets the realities of daily operations.

That is why the question is not which model is best in the abstract. It is which approach helps this organization make the next decisions clearly. A system rollout, a merger, a new operating model, and an AI initiative all change work in different ways. The model needs to match the load on people, the level of uncertainty, and the leadership behavior required to make the change credible.

Start with the problem, not the framework

Teams often choose a familiar framework before agreeing on the job it must do. That creates a polished project plan with a thin connection to the real work. Begin by asking what must be different when the change is working. Is the goal a new behavior, a new decision process, a new technology habit, or a new relationship between teams? Who will carry the heaviest part of the shift? What will make the old way hard to leave behind?

Then look at the conditions around the work. A change with a clear destination but weak local follow-through needs manager support and reinforcement. A change with several competing initiatives needs senior leaders to sequence the work and resolve tradeoffs. A change that asks people to rethink their role may require more listening and room for transition. Walt's guide to enterprise change management explains why those portfolio-level choices matter when several major efforts compete for the same people.

A visual map of possible routes through organizational change

Four change management models leaders should know

Lewin's three-stage model

Kurt Lewin's classic model is often summarized as unfreeze, change, and refreeze. Its value is its simplicity. Before asking people to adopt a new behavior, leaders help them understand why the old approach is no longer enough. They then support the move to the new way of working and reinforce it until it becomes part of normal operations.

This model is useful when a team needs a plain-language narrative for a defined change. It is less useful as a complete operating system for a large, multi-year transformation. In fast-moving environments, leaders should also be careful with the word "refreeze." The point is not to pretend work will never change again. It is to make the new behavior stable enough that people are not constantly rebuilding their routines. The Mind Tools overview of Lewin's model provides a concise explanation of the three stages.

Kotter's eight-step process

John Kotter's model gives leaders a more detailed sequence, from building urgency and a guiding coalition through communicating the vision, removing barriers, sustaining acceleration, and embedding the change. It is especially useful when a major initiative needs visible sponsorship across functions. The model reminds leaders that a launch message is not the same thing as broad commitment.

Kotter's strength is the attention it gives to leadership alignment and momentum. Its risk is treating the eight steps as a checklist that a project team can complete for everyone else. The steps only work when senior leaders make real decisions, managers can translate them locally, and teams can raise the problems that appear after the kickoff. Kotter's own description of the eight steps is a useful reference for the intended sequence.

Prosci's ADKAR model

ADKAR focuses on the individual journey through change: Awareness of the need, Desire to participate, Knowledge of how to change, Ability to apply new skills, and Reinforcement to sustain the behavior. It gives managers a practical diagnostic. If people understand the business reason but do not act, the problem may be desire, confidence, capacity, or an unresolved barrier, not more communication.

This approach works well when adoption depends on many people changing day-to-day habits. It makes the human side of change more concrete without reducing people to a status color on a dashboard. It is particularly helpful for technology adoption, new processes, and role-based training, where different groups may need different support. Prosci's ADKAR framework explains the five outcomes in more detail.

Bridges' Transition Model

William Bridges separates external change from the internal transition people experience. His model focuses on endings, the neutral zone, and new beginnings. That distinction is useful when a change affects identity, role, relationships, or a familiar way of working. A reorganization can be complete on an org chart while employees are still trying to understand what they are leaving behind and what the new expectations mean.

Leaders can use this lens to make room for honest questions. People do not need every answer on day one, but they do need to know what is settled, what is still being worked through, and where to get help. The neutral zone is not a failure of leadership. It is the period where people test whether the new direction is real and workable.

Leaders discussing practical options around a meeting table

How to choose a model that fits the work

Use the model as a starting point, then make four decisions. First, consider the scale. A small process change may only need a clear case for change, manager conversations, practical support, and reinforcement. A transformation affecting several functions requires a portfolio view, senior sponsorship, coordinated messages, and a way to pace the demands on teams.

Second, consider whether the work is primarily behavioral or structural. If the central challenge is new habits, ADKAR-style diagnosis can help leaders identify what is getting in the way. If the challenge is a broad strategic shift that needs leadership momentum, Kotter's focus on coalition and direction may be more useful. If teams need to leave behind a familiar role or operating identity, Bridges can make the transition visible. If a group needs a simple shared language, Lewin can be enough.

Third, consider the time horizon. Models should create a rhythm people can sustain. A framework that demands weekly ceremonies and lengthy artifacts may make sense for a complex transformation, but it can overwhelm a team trying to fix a clear operational problem. Finally, consider what leaders are actually prepared to do. No model can compensate for sponsors who will not make choices, managers who lack context, or a plan that ignores the workload it creates.

Questions that make the choice clearer

Before settling on a model, bring the sponsors, change leads, and a few managers into the same conversation. Ask what people will need to stop doing, start doing, or do differently. Ask where the current organization is most likely to get stuck. Is the risk a lack of urgency, competing priorities, unclear manager conversations, limited skills, or exhaustion from too many changes at once? A useful model should bring the hard question into the open early, while leaders can still adjust the path.

It also helps to define the smallest proof that the change is taking hold. For a new operating process, that may be a reliable handoff between teams. For a technology rollout, it may be consistent use in the moments that matter most. For an AI initiative, it may be a clear expectation for quality and accountability, not merely a count of logins. When teams know what adoption looks like in practice, they can use the model to remove barriers rather than report activity.

Include managers in this choice. They can identify where a polished framework will collide with customer commitments, staffing, existing measures, or an unresolved decision. That perspective does not weaken the model. It keeps leaders from mistaking agreement in a planning session for readiness in the work itself.

Do not stack models without a clear purpose

There is nothing wrong with combining ideas. Many strong change efforts use a simple leadership sequence, an individual adoption lens, and a practical manager toolkit. The problem starts when every function introduces its preferred model and expects the organization to learn all of them. People end up translating vocabulary instead of doing the work.

Choose one primary model as the shared language. Then borrow only the pieces that solve a real gap. For example, a leadership team could use Kotter to structure sponsorship and momentum, while managers use ADKAR questions to identify where employees need support. Make that choice explicit. Tell people what the model is for, what they are expected to use, and what they can ignore.

Turn the model into a working plan

A model earns its place when it changes the next meeting, the next message, or the next decision. Start with a short map of the people affected, the behaviors that need to change, the leaders who must show visible sponsorship, and the predictable barriers to adoption. Then set a rhythm for reviewing what teams are hearing and what needs to change in the plan.

That work becomes more manageable when leaders use focused change management activities instead of trying to launch every communication, training session, and report at once. Clarify the reason for the work, equip managers for local conversations, remove practical obstacles, and reinforce the new behavior. A model can guide the sequence, but it cannot replace the leadership choices within it.

A meeting room prepared for a practical change planning session

What to watch once the work begins

The test of a model comes after the kickoff. Watch for signs that the framework is helping people make decisions or merely giving them new labels. When managers can explain the change in their own words, teams know where to raise a barrier, and senior leaders make visible tradeoffs, the approach is doing useful work. When people spend more time debating the stages than solving the operating problem, it is time to simplify.

Pay close attention to mixed signals. A sponsor may ask for a new behavior while the performance measures, meeting agendas, and resource decisions continue to reward the old one. A rollout can call for learning while managers are given no time to let people practice. These are not communication problems alone. They are leadership decisions that determine whether the organization can trust the change.

Use a short recurring review to identify what has changed since the previous check-in: the questions people are asking, the barriers that remain, the groups under the most strain, and the decisions sponsors need to make. This is where the practical value of any model shows up. It gives leaders a disciplined way to listen, act, and keep the path credible without pretending the original plan anticipated everything.

A practical 30-day starting point

Name the change. Write a plain-language statement of what will be different and why it matters now.
Choose one shared model. Select the simplest approach that covers the real challenge, then explain how teams should use it.
Map the affected groups. Identify the behaviors, decisions, and workload changes each group will experience.
Set the sponsor rhythm. Decide what leaders will communicate, which decisions they own, and how they will hear feedback.
Prepare managers. Give them answers, escalation paths, and room to make the change relevant to their teams.

At the end of 30 days, ask a hard but useful question: are people clearer about the work, or have you simply produced more material about it? If clarity is not improving, simplify the approach before adding another layer.

How Walt Carter helps leaders make change workable

Walt Carter has led technology and operating transformations from executive roles including CIO, CDO, COO, and CMO. His keynotes and workshops help leadership teams replace abstract transformation language with the decisions and habits that create clarity, commitment, and action. For a high-stakes event or leadership session, explore options for event planners, watch Walt in action, or start a conversation with his team.

Frequently asked questions

What are the most common change management models?

Common models include Lewin's three-stage model, Kotter's eight-step process, Prosci's ADKAR model, and Bridges' Transition Model. They focus on different aspects of change, so the most useful choice depends on the decision, the people affected, and the amount of coordination required.

Which change management model is best?

There is no universally best model. A simple process change may need only a few clear steps and local manager support, while a major transformation needs leadership alignment, a portfolio view, and a way to reinforce new behavior over time.

Can leaders combine change management models?

Yes. Many organizations use one model to create a shared language and borrow practical elements from another. The important thing is that leaders make the approach clear, rather than giving teams several overlapping frameworks with no decision about how they fit together.

When should a company use a formal change management model?

A formal model is most helpful when a change affects many teams, changes daily work, creates uncertainty, or competes with other major priorities. It gives leaders a repeatable way to prepare people, involve managers, and respond to problems as the work moves forward.