If you’re about to lead a change initiative — an AI adoption project, a process overhaul, a digital transformation — you’ve probably been told to “pick a framework.” And then you find yourself staring at five or six options, each with its own acronym, its own diagram, and its own book deal, wondering which one is the right fit.

I’ve spent the last several weeks writing a detailed comparison of the five most popular change management frameworks and how they stack up against the 5P Framework by Trust Insights. I’m biased — I built the 5P Framework — but I’ve tried to be honest about what each model does well and where it falls short. Here’s the decision guide version.

When to Use ADKAR

Use ADKAR when your primary challenge is individual adoption. If the change depends on each person understanding, wanting, and being able to do something new, ADKAR gives you a clear psychological sequence to work through. It’s especially strong for technology rollouts where you need people to actually use the new tool — not just know it exists. I wrote more about what ADKAR gets right (and misses) here.

When to Use Kotter’s 8 Steps

Use Kotter when you need organizational momentum. If the change requires executive buy-in, cross-functional alignment, and visible early wins to build credibility, Kotter gives you a playbook for moving an entire organization. It’s best suited for large-scale transformations where the biggest risk is inertia. Here’s where it stops short.

When to Use Lewin’s Model

Use Lewin when you need a simple mental model for understanding resistance. Unfreeze-Change-Refreeze is useful as a conceptual lens, especially for cultural or behavioral shifts. But — and this is a big but — you’ll need to pair it with something more operational for actual project execution. Three phases isn’t enough on its own.

When to Use McKinsey 7-S

Use McKinsey 7-S when you need a diagnostic tool. If you suspect organizational misalignment is the root cause of your problems, 7-S gives you a structured way to assess seven interconnected dimensions. It’s a snapshot, not a roadmap — so you’ll need an action framework to follow up. Here’s why diagnosis alone isn’t enough.

When to Use Bridges’ Transition Model

Use Bridges when you need to focus on the emotional experience of change. If your team is going through grief, uncertainty, or fear about the future, Bridges gives you language and structure for supporting them through the psychological transition. It’s the most human model on this list. But empathy needs structure to produce results.

When to Use the 5P Framework

Use the 5P Framework when you need all of the above to actually lead somewhere.

The 5P Framework isn’t competing with these models — it’s the structural wrapper that makes them measurable. Start with Purpose: the measurable question your change is trying to answer. Then address People (use ADKAR or Bridges here if you need individual-level or emotional support). Define your Process (use Kotter here if you need organizational momentum). Select the right Platform. And close with Performance — measuring whether you actually achieved what you set out to do.

The best approach isn’t to pick one framework and hope it covers everything. It’s to start and end with measurement, and use the right tools for the middle.

The Moral of the Story

Stop asking “which framework should I use?” and start asking “what measurable question am I trying to answer?” Once you have that, pick the tools that serve each layer of the work — and bookend the whole thing with Purpose and Performance so you know whether it actually worked.

For the full side-by-side comparison with the detailed strengths-and-gaps analysis: The 5P Framework vs. Other Change Management Models.

Ready to put the 5P Framework to work? Start with Change Management, AI Strategy, or Getting Started — whichever matches where you are right now.

I’ve watched dozens of change management projects follow a framework to the letter and still end up in the same place: no one can tell you whether it actually worked.

Not because people didn’t try. Not because the framework was bad. Because no one asked the two questions that matter most.

Question One: “What Are We Trying to Answer?”

Before you build a coalition, before you create urgency, before you unfreeze anything — you need a measurable question. Not a goal statement. Not a vision. Not something that sounds good in a town hall. A question that has a specific, measurable answer.

“How do we increase customer retention by 15% over the next two quarters?” is a measurable question. “Improve the customer experience” is not. The first one tells you exactly what to measure and when to measure it. The second one could mean literally anything, and six months from now everyone will claim success based on whatever metric makes them look good.

The difference between these two starting points determines whether you’ll be able to evaluate the project at all.

And here’s what gets me: most change management frameworks skip this step entirely. ADKAR starts with Awareness. Kotter starts with Urgency. Lewin starts with Unfreeze. Bridges starts with Ending. All valid starting points for their respective purposes. But none of them require you to define what success looks like in measurable terms before you begin. They assume someone has already done that. And in my experience? Someone usually hasn’t.

Question Two: “Did We Answer It?”

This is the question that almost never gets asked. Projects end. The new process gets adopted. The tool gets rolled out. Everyone moves on to the next fire. And nobody circles back to check whether the original question got answered.

Kotter’s final step is “Institute Change” — embedding the change into culture. ADKAR ends with Reinforcement — making the change stick. Both important. Neither one is the same as measuring whether the change produced the outcome you set out to achieve.

You can reinforce a change that didn’t work. You can institutionalize a process that doesn’t solve the problem. “It stuck” and “it worked” are two very different things.

I’ve lived this. I’ve been in the room at the end of a major initiative where everyone is congratulating themselves and I’m the one asking “but did we hit the number?” And the room goes quiet. Not because they don’t care — because they genuinely don’t have an answer. The project didn’t fail. It just never had a way to prove it succeeded.

The Framework That Forces Both Questions

The 5P Framework by Trust Insights was built to close this gap. It starts with Purpose — your measurable question — and ends with Performance — the answer to that question. Everything in between (People, Process, Platform) serves the Purpose and gets validated by Performance.

Two questions. That’s the difference between a project that “went well” and a project that actually worked.

The Moral of the Story

Every framework has value. But no framework works if you don’t know what you’re trying to achieve and you don’t check whether you achieved it. Start with a measurable question. End with a measurable answer. Everything else is the work in between.

For the full side-by-side comparison of how five major models handle (or don’t handle) these two questions: The 5P Framework vs. Other Change Management Models.

Ready to put the 5P Framework to work? Start with Change Management or go to Getting Started for the full walkthrough.

It’s the most recognized change management playbook in the corporate world. But recognition doesn’t mean it’s finished.

Kotter’s 8-Step Process for Leading Change is probably the most recognizable change management framework in the corporate world. Urgency, coalition, vision, communication, empowerment, short-term wins, consolidation, institutionalization. It’s comprehensive, it’s sequential, and it’s been taught in business schools for decades. If you’ve ever sat through a leadership offsite about “driving transformation,” someone had Kotter on a slide.

And I have a lot of respect for this model. It gets something right that many others don’t: organizational momentum. The emphasis on building a guiding coalition and generating short-term wins is practical and powerful. If you’ve ever tried to push through a transformation without executive buy-in or visible early results, you know exactly why those steps matter. People need to see proof that the change is real and that leadership is behind it. Kotter understood that.

He also understood that change is a leadership problem, not just a management problem. The distinction between “create urgency” and “write a project plan” is enormous. Kotter is telling you to move people emotionally before you move them operationally. That’s smart.

But There’s a Structural Problem

Here’s the thing. Kotter’s model starts with urgency. Not with a clearly defined, measurable goal. Urgency is about emotional energy — getting people to feel that change is necessary. That’s useful, but it’s not the same as stating what specific outcome you’re trying to achieve and how you’ll know if you got there.

I’ve seen this play out more times than I can count. Leadership team gets fired up. They rally the troops. They build a coalition. They communicate a vision. And the vision is something like “become an AI-first organization” or “transform the customer experience.” Which sounds great in a town hall. But when you ask “how will we know if this worked?” the room goes quiet.

That’s not a Kotter problem, exactly — it’s a problem with how organizations use Kotter. But a framework should make it hard to skip the critical step, not easy.

And then there’s the ending. The final step — “Institute Change” — is about embedding new behaviors into the culture. That’s important. But it’s not the same as measuring whether the change produced the result you originally set out to achieve. You can successfully embed a new process into your culture and still have no idea whether it actually moved the needle on the business problem you were trying to solve.

You institutionalized a change. Great. Did it work? (Crickets.)

The Missing 9th Step

What Kotter’s model needs is a bookend on each side. A measurable purpose at the start and a performance review at the end. That’s exactly what the 5P Framework by Trust Insights provides.

Purpose asks: “What specific, measurable question are we trying to answer?” Not a vision statement. Not an aspiration. A question with a number attached to it. Performance asks: “Did we answer it?” Not “did people adopt it?” Not “did it stick?” — “Did it actually produce the outcome we said it would?”

So here’s what I actually recommend: you can run Kotter’s 8 steps inside the 5P Framework. Use Kotter for organizational alignment, coalition building, and momentum — it’s excellent for that. But start with Purpose so you know what success looks like before you create urgency around it. And end with Performance so you can actually prove the initiative was worth the disruption.

Eight steps is a lot to execute. A lot of meetings. A lot of energy. A lot of political capital spent. You deserve to know at the end whether they worked.

The Moral of the Story

Kotter built a great playbook for moving an organization through change. But he assumed someone had already defined what success looked like, and he didn’t build in a step for checking whether you got there. The 5P Framework adds those bookends: start with a measurable question, end with a measurable answer.

If you want the full side-by-side breakdown of how Kotter stacks up against ADKAR, Lewin, McKinsey 7-S, and Bridges, I wrote the whole comparison: The 5P Framework vs. Other Change Management Models.

Ready to see how the 5P Framework applies to change management specifically? Start here.

Kurt Lewin’s Unfreeze-Change-Refreeze model is the oldest formal change management framework still in active use. Published in the 1940s, it introduced a deceptively simple idea: before you can change a system, you have to destabilize it. Then you make the change. Then you stabilize the new state.

It’s elegant. It’s intuitive. And for certain types of change — especially cultural or behavioral shifts — the metaphor still holds up. The concept of “unfreezing” is a genuinely useful lens for understanding organizational resistance. People aren’t resisting change because they’re difficult. They’re frozen in patterns that have worked for them until now. You have to acknowledge that before you can move them.

I use this metaphor all the time when I’m explaining to leadership teams why their shiny new initiative isn’t getting traction. “You haven’t unfrozen anything. You just dropped a new tool on people and expected them to reorganize their entire workflow overnight.” That’s a Lewin insight, and it’s a good one.

But Simplicity Has a Cost

Here’s the thing. Lewin’s model is a three-phase conceptual framework, not an operational one. It tells you the shape of change but gives you almost nothing to work with in terms of execution.

There’s no guidance on how to assess your people’s skills, willingness, or psychological safety. There’s no process for documenting repeatable workflows. There’s no mechanism for selecting the right tools or platforms. And there’s no way to measure whether the change actually achieved what it was supposed to.

“Refreeze” means the new state has stabilized. It doesn’t mean the new state is better. You can successfully refreeze around a process that doesn’t solve the problem you started with. You can stabilize into something that’s just as broken as what you had before — it’s just a different kind of broken. And Lewin’s model gives you no way to tell the difference.

I also have a practical objection: in 2026, does anything ever really “refreeze”? The pace of change in most organizations means you’re unfreezing again before the last change fully solidified. Lewin was writing in the 1940s. The idea that you could reach a stable new state and stay there for a meaningful period of time was a lot more reasonable then than it is now.

What 80 Years of Practice Has Taught Us

Lewin was ahead of his time. But the world has gotten more complex, and change management needs more structure than three phases can provide. The 5P Framework by Trust Insights builds on the same intuition — that change needs to be deliberate and phased — but adds the specificity that Lewin’s model lacks.

Purpose defines what you’re changing and why, in measurable terms. People addresses the skills, willingness, and psychological safety of your team (this is where the “unfreeze” work actually lives). Process maps the workflows that need to change. Platform ensures you’re choosing the right tools. And Performance closes the loop by measuring whether the change actually worked — not just whether it stabilized.

So here’s my recommendation: use Lewin’s Unfreeze-Change-Refreeze as a mental model for the emotional arc of transformation. It’s a good lens. But pair it with the 5P Framework so you have operational structure, clear measurement, and a way to prove the investment was worth it.

Because “we successfully refroze” is not the same thing as “it worked.” And after 80 years, we should probably expect a framework to tell us the difference.

The Moral of the Story

Lewin gave us a foundational metaphor. It’s still useful. But a metaphor isn’t an operating system. If you need to actually manage a change initiative — with people, processes, tools, and measurable outcomes — you need more than three phases and an ice cube analogy.

For the full comparison of how Lewin stacks up against ADKAR, Kotter, McKinsey 7-S, and Bridges: The 5P Framework vs. Other Change Management Models.

Want to see what a complete change management framework looks like? Start with the 5P Framework for Change Management.

The McKinsey 7-S Framework is one of those models that looks impressively comprehensive on a slide deck. Strategy, Structure, Systems, Shared Values, Skills, Style, Staff. Seven interconnected elements that all need to be aligned for an organization to function effectively.

And it’s right. Organizational alignment does matter. If your strategy says one thing and your systems do another, you’ve got a problem. The 7-S model is genuinely useful as a diagnostic tool — a way to assess where misalignment exists within an organization. I’ve used it in exactly that context: “let’s map these seven dimensions and see where the cracks are.” It works for that.

It’s also the framework that most explicitly addresses organizational culture (Shared Values, Style) as a factor in change. A lot of models ignore culture entirely. McKinsey at least puts it on the diagram.

The Limitation Nobody Mentions

Here’s the thing. McKinsey 7-S is a snapshot, not a roadmap. It tells you what to examine, but it doesn’t tell you what to do once you’ve found the misalignment. There’s no sequence. There’s no prioritization. There’s no process for deciding which element to address first or how to manage the change from state A to state B.

I’ve sat in rooms where teams have done a thorough 7-S analysis. They’ve mapped all seven dimensions. They’ve identified the misalignments. And then someone says, “Okay, so… now what?” And the room goes quiet. Because the framework gave them a diagnosis with no treatment plan.

It also doesn’t start with a measurable purpose. You’re assessing alignment against… what, exactly? If you haven’t defined what success looks like before you start analyzing seven organizational dimensions, you’re generating a lot of insight with no clear direction for what to do with it. You end up with a really thorough slide deck and no next step.

And like every other major framework I’ve reviewed, it doesn’t close the loop. There’s no built-in mechanism for measuring whether your realignment efforts actually produced the outcome you were after. You can realign all seven S’s and still not know if the business problem got solved.

From Diagnosis to Action

The 5P Framework by Trust Insights isn’t competing with McKinsey 7-S — it’s completing it. Use 7-S to diagnose organizational alignment. Then use the 5P Framework to act on what you find.

Start with Purpose: define the measurable question your realignment is trying to answer. Then map the 7-S insights to the 5P structure. Skills, Staff, and Style map to People. Systems and Structure map to Process. The tools and technology that support your Strategy become Platform. And Performance measures whether the realignment actually produced the outcome you defined in Purpose.

Now you’ve got something. A diagnosis and a treatment plan. A before and an after. A question and an answer.

The Moral of the Story

Diagnosis is valuable. I’m not dismissing it. But without a framework for action and measurement, it stays on a slide deck instead of driving real change. McKinsey 7-S tells you where you’re misaligned. The 5P Framework tells you what to do about it and how to know if it worked.

For the full side-by-side comparison: The 5P Framework vs. Other Change Management Models.

Want to move from diagnosis to action? The 5P Framework for Change Management is where to start.

William Bridges’ Transition Model is different from most change management frameworks, and I mean that as a genuine compliment. While everyone else is focused on the operational mechanics of change — steps, phases, alignment diagrams — Bridges focuses on the psychological experience. Ending, Neutral Zone, New Beginning. It’s about what people go through internally when the world around them shifts.

If you know me, you know I believe people come first. Always. So a model that centers the human emotional experience of change? I’m here for it.

The Neutral Zone, in particular, is an underappreciated concept. That messy, uncertain period where the old way is gone but the new way hasn’t fully taken hold. Most project plans pretend this phase doesn’t exist. They go from “launch new system” to “adoption complete” with nothing in between. Bridges names the thing that every person who’s ever lived through a reorg already knows: there’s a disorienting middle where nobody knows what the rules are anymore. Acknowledging that — planning for it — is valuable.

Where It Falls Short

Here’s the thing. Bridges’ model is entirely focused on the emotional journey. It doesn’t address skills. It doesn’t address tools. It doesn’t address processes or workflows. It doesn’t start with a measurable purpose, and it doesn’t end with any way to evaluate whether the transition led to a better outcome.

“New Beginning” means people have psychologically accepted the change. It doesn’t mean the change worked. Your team could move through Ending, Neutral Zone, and New Beginning with flying colors and still be operating a process that doesn’t solve the original business problem. Everyone feels great about the transition. The numbers haven’t moved. Now what?

Bridges also doesn’t give you any operational structure. If you’re managing a real project — with timelines, deliverables, technology decisions, and stakeholder reporting — you need more than an emotional roadmap. You need to know who’s responsible for what, what the workflow looks like, which tools you’re using, and how you’ll measure success. Bridges doesn’t touch any of that.

I’ve seen well-meaning leaders invest heavily in supporting their teams through the emotional transition and completely neglect to document the new process or measure whether the change delivered results. The team felt cared for. The project had no measurable outcome. That’s not a win — it’s a missed opportunity.

Combining Emotional Intelligence with Operational Structure

The 5P Framework by Trust Insights and Bridges’ Transition Model are natural complements. Bridges gives you a lens for the People layer of the 5P Framework — understanding where your team is emotionally and what support they need to move forward. That’s the “unfreeze” work, the “Neutral Zone” management, the emotional intelligence piece. It’s real and it matters.

But the 5P Framework wraps that emotional intelligence in operational structure. Purpose defines what you’re trying to achieve in measurable terms — before you start managing anyone’s feelings about the change. Process maps the workflows. Platform selects the right tools. And Performance measures whether the whole effort — emotional transition included — actually delivered results.

Use Bridges for the People layer. Use 5P for everything else. Now you’re managing the whole picture: how people feel and whether the project worked.

The Moral of the Story

Feelings matter. But so do outcomes. The best change management approach addresses both. Bridges gives you the empathy. The 5P Framework gives you the structure, the measurement, and the proof.

For the full side-by-side comparison of all five models: The 5P Framework vs. Other Change Management Models.

Ready to see what operational structure plus emotional intelligence looks like? The 5P Framework for Change Management.

It’s one of the most popular change management models for a reason. But popularity doesn’t mean it’s complete.

If you’ve ever been part of a change management initiative — and if you’re reading this, you probably have — there’s a good chance someone pulled out the ADKAR model. Awareness, Desire, Knowledge, Ability, Reinforcement. It’s been the go-to framework in corporate change management for years, and I get why.

I’ve used ADKAR. I’ve recommended ADKAR. And I think it does something genuinely important that a lot of other models skip over entirely: it addresses willingness. The “Desire” step forces you to acknowledge that people don’t just need to understand the change — they need to actually want to participate in it. That’s not a small thing. Most models assume that if you explain the change clearly enough, people will just get on board. Anyone who has ever managed a team knows that’s not how humans work.

ADKAR also gives you a diagnostic. If someone isn’t adopting the change, you can pinpoint exactly where they’re stuck — is it Awareness? Desire? Knowledge? — and address that specific barrier. That’s practical. That’s useful. I’m not here to trash it.

So What’s Missing?

Here’s the thing. ADKAR starts with Awareness. That means it assumes someone has already figured out what the change is and why it matters. But in practice? That step gets skipped more often than you’d think.

Teams jump into building awareness for a change initiative that was never clearly defined in measurable terms. They can tell you they’re “adopting AI” or “improving customer experience,” but they can’t tell you what specific, measurable question the project is trying to answer. “We’re rolling out a new CRM” is not a purpose. “What is the impact of our CRM migration on sales cycle length?” — that’s a purpose.

And it doesn’t just have a gap at the beginning. It has one at the end, too.

Reinforcement — the final step — is about making the change stick. It’s about sustaining adoption. That’s valuable. But it’s not the same thing as measuring whether the change actually produced the outcome you set out to achieve. You can reinforce a change that didn’t work. You can sustain adoption of a tool that isn’t solving the problem it was supposed to solve. Reinforcement asks “did people stick with it?” It doesn’t ask “did it actually work?”

That’s two missing bookends: no measurable purpose at the start, and no performance measurement at the end.

How the 5P Framework Fills This Gap

This is where I’m biased, and I’m not even humble about it. The 5P Framework by Trust Insights — which I built — bookends the entire process with Purpose and Performance. Purpose forces you to state a measurable question before you do anything else. Performance forces you to go back and answer it. Everything in between — People, Process, Platform — serves the Purpose and gets validated by Performance.

So here’s what I actually recommend: you don’t have to abandon ADKAR to use the 5P Framework. Use them together. ADKAR is excellent for the People layer — it gives you a diagnostic for individual adoption that the 5P Framework doesn’t try to replicate at that level of detail. But wrap it in 5P so that the work you’re doing has a defined starting point and a measurable finish line.

Start with Purpose: what measurable question are we trying to answer with this change? Then use ADKAR to get your People through the adoption curve. Document your Process. Select your Platform. And close with Performance: did we answer the question we started with?

Because if you can’t answer “did this actually work?” at the end, the framework didn’t fail. The project just never had a way to succeed.

The Moral of the Story

ADKAR is a good model. It earned its place. But it was designed to manage individual adoption, not to structure an entire change initiative from purpose to proof. If you’re using it as your only framework, you’re missing the two questions that matter most: “What are we actually trying to achieve?” and “Did we achieve it?”

The 5P Framework gives you both. And if you want to see how ADKAR stacks up against Kotter, Lewin, McKinsey 7-S, and Bridges in a side-by-side comparison, I wrote the whole thing out: The 5P Framework vs. Other Change Management Models.

Want to see where your organization stands? Start with the 5P Framework for Change Management — it’ll walk you through exactly where to begin.