Types of Change Management Models: A Practical Guide for 2026

Most organizations don’t fail at deciding to change. They fail at executing it. A new system gets deployed, a process gets redesigned, and six months later people are still doing things the old way — because no one treated the human side of the transition as seriously as the technical side.

That is where change management models become practical tools, not academic theory. These frameworks exist because organizational change follows predictable patterns. Having a structured way to manage those patterns means better outcomes, faster adoption, and far less resistance along the way. But a framework on paper only goes so far — what employees actually need is guidance in the flow of their work, at the exact moment a new process or system demands something different from them.

This guide covers the most widely used types of change management models, how each one works in practice, and which scenarios each one fits best.

TL;DR

The most widely used types of change management models in 2026 include:

For enterprise software rollouts and digital transformation programs, ADKAR and Kotter’s model are the most commonly applied because they focus on individual behavior change and measurable adoption milestones.

Why Change Management Models Matter More in 2026

Change without structure creates friction. Teams don’t know what’s coming, training gets rushed, and adoption stalls because no one accounted for resistance early enough.

But the stakes in 2026 are higher than they were five years ago. Organizations are rolling out AI-powered tools, replacing legacy ERP and CRM systems, and restructuring workflows faster than most employees can absorb. In 2026, 71% of organizations plan to increase spending on AI technologies — which means change volume is accelerating, and without structured frameworks to manage the human side of that change, the ROI on those investments stays theoretical.

According to Deloitte’s State of AI in the Enterprise report, two-thirds of organizations report productivity and efficiency gains from enterprise AI adoption — but only the organizations that pair technology investment with structured change management actually sustain those gains.

For large enterprises especially, the cost of poor adoption doesn’t just show up in IT tickets. It shows up in compliance gaps, productivity loss, and software investments that never deliver their expected return. When you’re rolling out a new ERP, CRM, or HRMS system across thousands of employees, organizations that close this gap typically invest in both a change framework and an in-application guidance layer that supports employees where the work actually happens.

Change management models give organizations a repeatable approach to avoid that outcome. They bring structure to what is otherwise a messy, unpredictable process — and they give change leaders a shared language to align stakeholders, set expectations, and measure progress.

Without a framework, change becomes a series of one-off decisions made under pressure. With one, it becomes a managed process with defined stages, clear accountabilities, and predictable pressure points that teams can prepare for in advance.

7 Types of Change Management Models You Should Know

1. Lewin’s 3-Stage Change Management Model

Developed by psychologist Kurt Lewin in the 1950s, this model breaks organizational change into three stages: Unfreeze, Change, and Refreeze.

Unfreeze is the preparation phase. Before any change can take hold, the current state needs to be disrupted enough that people understand why the change is necessary. This includes leadership communication, data transparency, and creating genuine urgency around the problem being solved.

Change is the implementation stage. New processes, tools, or behaviors are introduced. This is where training, support, and step-by-step guidance matter most. Employees need to know not just that things are changing but how to navigate the new way of working — ideally with contextual support available inside the applications they use daily, not just in a training room they visited once.

Refreeze is about making the new way stick. Once changes are adopted, they need to be reinforced through revised processes, updated documentation, and ongoing support until the new behavior becomes the default rather than the exception.

2. Kotter’s 8-Step Change Model

John Kotter’s framework, developed at Harvard, is one of the most referenced in enterprise change management. It focuses heavily on leadership behavior and organizational momentum rather than just process steps.

The eight steps are:

1. Create a sense of urgency
2. Build a guiding coalition
3. Form a strategic vision and initiatives
4. Enlist a volunteer army
5. Enable action by removing barriers
6. Generate short-term wins
7. Sustain acceleration
8. Institute change

What makes Kotter’s model valuable is its attention to culture and buy-in. Getting hundreds of people to change how they work requires more than a training session. It requires visible leadership, early wins that build credibility, and a coalition of champions who influence peers at the ground level.

3. ADKAR Change Management Model

Developed by Prosci, ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. Unlike process-focused frameworks, ADKAR operates at the individual level, which is why it’s particularly useful during software implementations and enterprise application rollouts.

• Awareness of why the change is needed
• Desire to participate and support the change
• Knowledge of how to change
• Ability to demonstrate the new skills
• Reinforcement to sustain the change

Each stage is a prerequisite for the next. If employees have awareness but no desire, training won’t help. If they have knowledge but lack ability, the process breaks down exactly when it matters most — in the daily workflow. This is why the Knowledge and Ability stages are where most enterprise rollouts stall. Employees leave training with information but no in-the-flow guidance when they sit down to actually do the work.

4. McKinsey 7-S Framework

This framework, developed by Tom Peters and Robert Waterman at McKinsey, is less about executing change and more about assessing organizational readiness for it. The 7 Ss are: Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff.

The model’s value is diagnostic. Before implementing change, organizations can use it to identify misalignment across these dimensions. A company might have a sound strategy but a structure that works against it. Or the right skills distributed in the wrong roles. Catching those gaps early prevents larger failures during execution.

5. The Bridges Transition Model

William Bridges made a critical distinction that most change models miss: change is situational, but transition is psychological. His model focuses on how people internally process change, not just what externally happens to them.

The Bridges model has three phases:

• Ending, Losing, and Letting Go — the emotional cost of leaving the old way behind
• The Neutral Zone — the ambiguous middle where the old way is gone but the new way isn’t fully established
• The New Beginning — genuine acceptance and engagement with the change

Where other frameworks focus on steps and milestones, Bridges emphasizes that people move through these emotional stages at different paces. Change managers who ignore this dimension create transitions where employees technically adopt a new system but remain disengaged underneath — which shows up in low utilization rates and high support ticket volumes months after go-live.

6. The Kübler-Ross Change Curve

Originally developed as a grief model, the Kübler-Ross curve was adapted for organizational change because the emotional arc turns out to be predictably similar. Employees typically move through denial, frustration, depression, experimentation, and eventually integration.

Understanding this curve helps managers predict where resistance will spike and plan support accordingly. The dip in the middle — often called the ‘valley of despair’ — is where most change initiatives fall short not because of bad strategy but because the daily experience employees have with new tools and processes isn’t supported properly; you can learn more about how organizations address this gap with structured approaches.  

7. The Satir Change Model

Virginia Satir’s model maps how people experience the performance impact of change over time. It tracks the journey from a stable ‘Late Status Quo’ through a ‘Foreign Element’ — the disruptive change — then into chaos, followed by integration, and finally a ‘New Status Quo’ at a higher performance level.

The key insight is that performance drops before it improves. This is predictable and manageable if you account for it. Organizations that expect immediate performance gains after a system rollout often pull support too early, right when employees need it most.

How to Choose the Right Change Management Model

There is no universal answer here. The right model depends on what kind of change is happening, who is affected, what the organization’s biggest risk is, and how much time exists to prepare. Picking the wrong framework doesn’t just waste effort — it creates misalignment between how leaders are thinking about the change and how employees are actually experiencing it.

A few questions worth working through before committing to a model:

Is this change primarily structural or behavioral?

Structural changes — reorganizations, system migrations, process redesigns — need frameworks that map clear steps and accountabilities. ADKAR and Kotter’s model work well here because they give change managers concrete milestones to track. Behavioral changes — culture shifts, leadership style, ways of working — need frameworks that address the emotional and psychological side of transition. That’s where Bridges and Kübler-Ross become more relevant.

How large and distributed is the affected population?

For a team of 20, a lightweight approach may be enough. For an enterprise rollout touching thousands of employees across multiple regions, you need a model that accounts for leadership alignment, communication at scale, and localized support. Kotter’s 8-Step model was specifically designed with large-scale organizational change in mind, which is why it remains one of the most referenced frameworks in enterprise transformation programs.

How much resistance do you expect?

If the change involves significant loss — familiar tools going away, roles changing, processes being eliminated — resistance will be higher. In those situations, the Bridges Transition Model and the Kübler-Ross Change Curve help managers understand where resistance will peak and how to address it before it stalls adoption. Ignoring the emotional dimension of change is one of the most common reasons enterprise rollouts underperform despite strong technical execution.

Is this a one-time transition or ongoing change?

Lewin’s model works best when there is a clear beginning, middle, and end. Organizations going through continuous change — frequent system updates, evolving processes, AI-driven workflow changes — need frameworks flexible enough to handle iteration rather than a fixed three-stage structure.

What does success look like — organizationally or individually?

If success means employees are actually using a new system correctly and consistently, ADKAR is the most precise tool available because it tracks adoption at the individual level. But tracking alone isn’t enough — employees need step-by-step walkthroughs, contextual tooltips, and user behavior analytics that show where people are struggling before those struggles become habits. If success means the entire organization has shifted its operating model, Kotter’s or McKinsey 7-S gives you the broader lens.

Here’s a quick reference to match scenarios with models:

One thing worth noting: most experienced change managers don’t pick one model and ignore the rest. ADKAR handles individual adoption milestones while Kotter’s framework drives leadership alignment and organizational momentum at the same time. McKinsey 7-S might be applied in the diagnostic phase before either of those kicks in. The frameworks complement each other when applied with clear intent.

The mistake most organizations make is defaulting to whichever model someone on the team has heard of rather than matching the framework to the actual problem. That’s where change initiatives lose coherence early — not because the model is wrong in theory, but because it was never the right fit for the specific transition at hand.

Change Management Trends Shaping How Organizations Apply These Models in 2026

The frameworks themselves haven’t changed dramatically. What has changed is the environment in which they’re being applied — and that context matters when deciding how to structure a change program today.

AI is creating a new category of change fatigue.

Organizations are no longer managing one transformation at a time. They’re rolling out AI tools, updating existing platforms, and restructuring workflows simultaneously. A clear shift is underway toward people-centered, AI-enabled change — one of the defining trends shaping organizations today. This means ADKAR’s Desire and Ability stages are harder to achieve because employees are being asked to absorb more change, faster, with less recovery time between initiatives.

Continuous change is replacing project-based change.

The traditional model of implement, stabilize, move on no longer holds. System updates happen quarterly. Process changes happen in response to market shifts. Organizations are moving toward smaller, faster, more agile change cycles that deliver value continuously — which means Lewin’s Refreeze phase is becoming less applicable on its own, and frameworks that support ongoing reinforcement and behavior tracking are gaining relevance.

Data-driven change management is replacing instinct-based decisions.

Change leaders in 2026 are expected to show adoption metrics, not just activity reports. Which teams completed training isn’t enough. Stakeholders want to see whether employees are actually working in the new system correctly, where drop-off is happening in the workflow, and which friction points need intervention. This shift favors frameworks like ADKAR and Satir that produce trackable milestones over frameworks that are purely qualitative.

The execution layer is becoming the differentiator.

CEOs are concluding that AI adoption is no longer a technology problem but a workforce and management problem. The same logic applies to every major system change. The organizations getting the most out of their transformation investments are the ones investing as seriously in the execution layer as in the strategy layer. That means in-application guidance, adoption analytics, and real-time support tools that work inside enterprise software — not just alongside it. Guided walkthroughs, contextual tooltips, and time-to-competency tracking are becoming standard components of how mature change programs operate in 2026.

The Execution Gap: Where Change Management Models Break Down

Understanding a framework is one thing. Executing it at enterprise scale inside real software environments is another problem entirely.

Most change initiatives fall short not because of bad strategy but because the daily experience employees have with new tools and processes isn’t supported properly. Employees receive a training session, maybe a recorded walkthrough, and then they’re expected to work in a new system they’ve barely touched — without in-the-flow guidance, without step-by-step support inside the application, and without any mechanism to prevent process errors while competency is still being built.

This is where the model breaks down in practice. ADKAR’s Ability stage, Kotter’s Enable Action step, Lewin’s Change phase — they all assume that employees can actually do the new work in the new system without constant IT escalation or manager intervention. That assumption fails more often than it succeeds when organizations rely purely on pre-go-live training to carry the full adoption burden.

The gap between a well-designed change management plan and actual employee adoption is almost always an execution problem. Communication plans, training decks, and change readiness surveys are necessary — but they weren’t built to close the last mile of behavior change on their own. What bridges that gap is support that lives inside the workflow itself — contextual, available on demand, and tied directly to the tasks employees are trying to complete.

How In-the-Flow Guidance Supports Change Management Execution

This is where in-application guidance becomes a practical component of change management execution rather than an optional add-on.

When employees are navigating a new system — a new ERP workflow, a redesigned CRM process, an updated HRMS module — what they need in that moment isn’t a training video. They need step-by-step guidance inside the application they’re using, at the exact point where they’re uncertain. That kind of in-the-flow support directly addresses ADKAR’s Knowledge and Ability stages, Kotter’s Enable Action step, and the performance dip that Satir’s model predicts.

Organizations that build this execution layer into their change programs see faster time-to-competency, lower support ticket volumes during rollout, and higher workflow completion rates — because employees aren’t left to figure out the new system alone between training sessions.

Apty is a Digital Adoption Platform that delivers exactly this. During a software rollout or process transition, Apty provides guided walkthroughs, contextual tooltips, field-level guidance, user behavior analytics, and adoption insights directly inside enterprise applications — whether that’s Salesforce, Workday, SAP, Oracle, or any other platform an organization is deploying.

In the context of change management frameworks:

• For ADKAR: Apty’s guided walkthroughs support the Knowledge and Ability stages by walking employees through new workflows inside the application, reducing time-to-competency without pulling them out of their work context
• For Kotter’s model: Apty’s adoption analytics show where employees are struggling in real time — giving change leaders concrete data to demonstrate short-term wins and identify barriers before they become bigger problems
• For Lewin’s Refreeze stage: Apty reinforces the new way of working through contextual reminders, process validations, and error prevention prompts that stop employees from reverting to old behaviors as the change settles in
• For the Satir Change Model: Apty shortens the performance dip by reducing friction during the chaos phase — step-by-step guidance means less time stuck, fewer support tickets, and a faster path to the new status quo

The result is that change management plans translate into measurable adoption metrics — task completion rates, workflow adherence, time-to-competency — rather than remaining aspirational frameworks on a project slide.

Conclusion

Choosing a change management model isn’t the hard part. Most organizations have access to the same frameworks. The real differentiator is how well those frameworks translate into actual employee behavior change — particularly when the transition involves new enterprise software in a year when AI-driven change is accelerating faster than most organizations are prepared for.

Understanding which model fits your scenario is the first step. ADKAR works when individual adoption is the metric. Kotter’s model works when organizational momentum and leadership alignment are the priority. Bridges and Kübler-Ross work when resistance and emotional transition need active management. No single framework owns the full picture, which is why the most effective enterprise change programs combine models with deliberate intent rather than defaulting to one.

The second step is making sure the execution infrastructure matches the ambition of the plan. A well-designed change framework without a reliable way to support employees at the moment they need it most — inside the applications where work actually happens — will always fall short of its potential.

FAQ

1. What is a change management model?

A change management model is a structured framework organizations use to guide transitions — whether adopting new software, restructuring teams, or managing a merger. Different models focus on different dimensions: some map process steps, others address how individuals emotionally process change, and some assess organizational readiness before change begins.

2. What is the most widely used change management model?

ADKAR and Kotter’s 8-Step Model are the most frequently applied in enterprise settings. ADKAR is preferred for software and system rollouts because it tracks adoption at the individual level. Kotter’s model is used when large-scale cultural or structural change requires strong leadership alignment across multiple teams.

3. What is the difference between Lewin’s model and Kotter’s model?

Lewin’s model uses three stages — Unfreeze, Change, Refreeze — and works best for defined, linear transitions. Kotter’s model has eight steps and places stronger emphasis on leadership behavior, urgency, and building a coalition of change champions. Kotter’s is better suited for large enterprise transformations where cultural momentum is critical.

4. What is the ADKAR model in change management?

ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. It operates at the individual level, treating each element as a milestone an employee must reach before the next stage works. It is most commonly used in software rollouts because it maps directly to how people move from unfamiliarity with a new system to consistent, competent use.

5. How do change management models apply to software rollouts?

Change management models structure the communication, training, and support employees need to adopt new tools successfully. ADKAR is the most direct fit — it tracks whether employees have the knowledge, ability, and reinforcement to actually use a new system correctly. In practice, organizations pair ADKAR with in-application guidance tools that deliver step-by-step walkthroughs inside the software itself, reducing the gap between training and real-world task completion.