Lean Change vs Prosci/ADKAR, Kotter's 8 Steps, Lewin's 3-Stage Model, and ACMP. What each framework is, where it came from, what assumptions it makes — and which one actually fits the way your organization works.
Before comparing specific frameworks, it helps to understand what separates traditional change management thinking from modern approaches — and why the distinction matters in practice.
Most organizations have change practitioners trained in traditional methods. Most organizations also run projects in complex, uncertain environments where those methods create friction. That gap is what drove the development of Lean Change Management — not to replace everything that came before, but to offer a structurally different approach for a structurally different context.
Each framework reflects a set of assumptions about how change works, who drives it, and what "success" looks like. Here's what each one actually is.
The foundational change model: Unfreeze → Change → Refreeze. Lewin argued organizations must first destabilize the status quo (unfreeze), implement the change, then solidify the new state (refreeze). Elegant in its simplicity, and influential in virtually every change framework that followed.
The core assumption: Change is episodic — it has a beginning, middle, and end. Refreeze assumes a stable new state is achievable. In environments of continuous change, that assumption rarely holds.
Eight sequential steps for large-scale organizational transformation: create urgency, build a guiding coalition, form a strategic vision, enlist a volunteer army, enable action by removing barriers, generate short-term wins, sustain acceleration, and institute change.
The core assumption: Urgency is the primary motivator. Leadership coalitions drive change through structured phases. Lean Change uses Kotter's steps as a useful checklist of questions to ask — not a sequence to follow.
ADKAR is an individual-outcome model: Awareness → Desire → Knowledge → Ability → Reinforcement. Built on Prosci's benchmarking research, it gives change practitioners a shared vocabulary and assessment tool for tracking individual change readiness.
The core assumption: Individuals must move through outcomes in sequence. Awareness before desire, knowledge before ability. In fast-moving environments where the solution itself evolves, this sequential logic creates structural tension.
The Change Management Body of Knowledge (CMBoK) defines competencies and knowledge areas for change practitioners — not a step-by-step methodology, but a professional standard. ACMP's CCMP certification is the profession's primary credential.
The core assumption: Change management is a profession with definable competency standards. CMBoK covers what practitioners should know. It doesn't prescribe a specific methodology for how to practice.
Built from agile, lean, and Lean Startup thinking — not adapted to fit them. The core cycle is Insights → Options → Experiments: a non-linear, feedback-driven loop with no prescribed starting point. Change practitioners select from 136 Elements of Change to build a contextual approach — like combining elements in a periodic table.
The core assumption: Change is uncertain, context-dependent, and best navigated through experimentation and co-creation — not managed through a predetermined sequence of outcomes. Resistance is data, not an obstacle.
How the five major change management frameworks compare across the dimensions that matter most in practice.
| Dimension | Lewin | Kotter | Prosci / ADKAR | ACMP / CMBoK | Lean Change |
|---|---|---|---|---|---|
| Structure | 3 sequential stages | 8 sequential steps | 5 individual outcomes | Competency areas (non-sequential) | Non-linear feedback loop |
| Origin | Social psychology, 1940s | Business leadership, 1996 | Benchmarking research, late 1990s | Professional standard, 2014 | Agile + Lean Startup, 2014 |
| Primary focus | Group behavior | Leadership coalition | Individual readiness | Practitioner competency | Co-created experiments |
| Assumes end state is known | Yes | Yes | Yes | Varies | No — evolves |
| Handles continuous change | Poorly | Partially | With adaptation | Framework-agnostic | Designed for it |
| Agile environment fit | Low | Moderate | With sprint adaptation | Depends on method applied | High — native |
| Resistance framing | Driving/restraining forces | Barrier to remove | Gap in ADKAR to address | Stakeholder concern to manage | Data to act on |
| Co-creation emphasis | Low | Moderate (coalition) | Low | Moderate | Core principle |
| Practitioner certification | No | Kotter certified programs | Prosci CCP | ACMP CCMP | Lean Change facilitator licensing |
| Works in large enterprises | Conceptually yes | Strong track record | Strong track record | Standard used widely | Yes — used in 50+ countries |
| Available as body of knowledge | Academic literature | Books + certification | Prosci methodology | CMBoK standard | 136-element Lean Change OS |
Context always wins. The right framework depends on your environment, your team's existing training, and the nature of the change you're navigating.
Lewin's 3-stage model works well as a teaching tool or a starting framework for practitioners new to change. It's not a detailed methodology, but it provides a useful conceptual foundation for understanding why change is disruptive.
Kotter's 8 Steps is well-suited to large, leader-driven transformations where building a guiding coalition and creating organizational urgency are genuine challenges. Strong executive sponsorship makes Kotter more effective.
If your change team holds Prosci certifications and your organization has an established ADKAR vocabulary, there's genuine value in consistency. ADKAR's individual-outcome tracking is also useful for identifying specific adoption gaps in predictable, well-scoped changes.
The CMBoK is the best framework for defining what a change practitioner should know and be able to do. It's method-agnostic — you can apply any methodology while meeting ACMP's competency standard, including Lean Change.
Lean Change Management is the strongest fit when your organization runs agile delivery, when the solution will evolve as you learn, when co-creation matters, or when previous change efforts have felt like change theatre. The Insights-Options-Experiments cycle is designed for exactly this context.
Lean Change doesn't require you to abandon everything else. Many practitioners hold Prosci or ACMP certifications while applying Lean Change principles. The Lean Change OS includes 136 elements that incorporate ideas from Kotter, McKinsey 7S, Satir, and others — you compose what fits your context.
This page is written by the creator of Lean Change Management. That means we have a point of view. We've tried to represent each framework fairly — their strengths and their genuine limitations — but you should know where we're coming from.
Prosci's research base is real and its individual-outcome model provides genuine clarity in the right context. Kotter's coalition-building guidance has helped large organizations navigate significant transformation. Lewin's model has influenced everything that came after it for good reason.
What Lean Change offers is a different structural assumption — that change is uncertain, non-linear, and best navigated through experimentation and co-creation rather than managed through a predetermined sequence. That assumption is either right for your context or it isn't. We'd rather help you figure that out than sell you on the idea that one framework wins every time.
Want to go deeper? The Lean Change OS is a free, publicly accessible body of knowledge covering 136 Elements of Change across four dimensions. The Agile Change Management comparison post on the blog goes deeper on the Prosci vs Lean Change distinction specifically. And if you'd like to explore applying Lean Change in your organization, training courses are available for individuals and teams.
The Lean Change OS is free, publicly accessible, and used by change practitioners in 50+ countries. Start with the book, or explore the full body of knowledge.