Why Lewin’s three-stage model is cited, copied, and misunderstood
Lewin’s three-stage change model is everywhere in change management conversations. Many people repeat the unfreeze, change, refreeze sequence without asking where this lewin model genuinely fits inside modern organizations. That habit turns a powerful change theory into a shallow slogan that obscures both its strengths and its limits.
At its core, the Lewin change model describes how a system moves from one relatively stable state to another through a structured approach. The unfreeze stage loosens the status quo by surfacing tensions in the current state, while the change stage introduces new behaviors, processes, and structures that shift the organization. The refreeze stage then stabilizes the new state so that employees do not slide back into old behaviors once the immediate pressure of the project fades.
Critics argue that continuous transformation makes any linear change process obsolete in complex organizations. They point to agile delivery, rolling strategy reviews, and constant technology updates as evidence that a simple three-stage model cannot handle real organizational change. The criticism is partly right, yet it misses how a bounded project still follows a recognizable unfreeze change arc even inside a turbulent environment.
For a person seeking information about change management, the nuance matters because different changes behave differently. A policy update, an office move, or a payroll system replacement has a clear end state, so the lewin change sequence can guide an effective change plan. By contrast, a multi year cultural shift or a digital transformation portfolio requires more continuous approaches that complement rather than replace the classic change lewin logic.
Experienced consultants treat the Lewin change model modern application as a scalpel, not a hammer. They use the unfreeze stage to frame why the current state is no longer viable, then shape the change stage around specific behaviors and processes that must shift. Finally, they design the refreeze stage as a set of governance, metrics, and reinforcement mechanisms that protect the new organizational state while still allowing future adaptation.
Where a linear model still outperforms: bounded scope, clear end state
Not every organizational change is a swirling cloud of ambiguity and continuous disruption. Many changes in organizations remain bounded projects with a defined scope, a clear target state, and a fixed go live date. In those cases, the Lewin change model modern application can outperform more fluid frameworks because it matches how people actually experience the shift.
Consider an ERP implementation, a shared service center consolidation, or a new performance management process. Each project has a recognizable unfreeze stage where leaders challenge the status quo, explain the pain of the current state, and build support among employees for the upcoming changes. The change stage then unfolds through training, process redesign, and role clarity, while the refreeze stage locks in new behaviors through updated policies and performance measures.
In such projects, a linear change process helps executives and employees understand where they are in the journey. The lewin change sequence offers a simple narrative that complements more detailed methods such as the ADKAR model, which focuses on individual awareness, desire, knowledge, ability, and reinforcement. Used together, the lewin model and the ADKAR model can align organizational processes with personal behaviors, creating more effective change outcomes.
Bounded initiatives also benefit from the structured approach of unfreeze change and change refreeze cycles. For example, when a bank centralizes its branch back office work, the organization can define a clear refreeze stage with new standard operating procedures and performance dashboards. That refreeze stage does not mean freezing the organization forever, but it does mean stabilizing the new processes long enough to measure results and adjust.
For consultants advising self organizing teams in change management, this clarity is valuable. Teams can experiment within the change stage while still recognizing that a refreeze stage will eventually set the new baseline for future continuous improvement. A detailed analysis of self organizing teams in change management, such as the one presented in this deep dive on outcomes of self organizing teams, shows that even highly adaptive groups benefit from a clear before and after when the stakes are high.
Where Lewin breaks down: continuous change and emergent strategy
Some environments simply do not sit still long enough for a classic unfreeze, change, refreeze sequence. When organizations operate with rolling product releases, quarterly system updates, and constant process tweaks, the Lewin change model modern application faces real limits. In these settings, the organization never fully reaches a stable state, so the refreeze stage becomes more metaphor than reality.
Continuous change creates a different rhythm for employees and leaders because the change stage never really ends. The status quo is always provisional, and the current state is just a temporary waypoint in a longer journey of organizational change. Under these conditions, a linear change process can feel artificial, and people may resist yet another unfreeze stage because they never had time to refreeze after the last wave.
Emergent strategy adds another layer of complexity, as leaders adjust direction based on market signals, data, and experimentation. Here, the lewin change model must be blended with iterative methods, agile ceremonies, and feedback loops that treat behaviors and processes as evolving prototypes. The ADKAR model can again complement this by tracking individual readiness across multiple overlapping changes rather than a single project.
For transformation portfolios, consultants often replace a single refreeze stage with a series of micro refreezes. Each micro refreeze stage stabilizes a specific process or behavior just enough to extract value and measure ROI, while leaving room for the next change stage to build on that foundation. Tools such as the Army Medical Quad Chart, adapted for change management, help leaders maintain running estimates of risks, benefits, and stakeholder impacts across these overlapping cycles, as illustrated in this practical example of running estimates.
In such contexts, the Lewin change model modern application shifts from being the primary change model to becoming a conceptual anchor. It reminds leaders that even in continuous environments, people still experience a psychological unfreeze stage when they question the current state, a change stage when they experiment with new behaviors, and a refreeze stage when those behaviors become the new normal. The art lies in shortening these cycles and layering them without overwhelming employees or undermining organizational support.
A decision framework: when to use Lewin, when to go iterative
Senior consultants need a clear decision framework to choose between a linear lewin model and more iterative approaches. The first diagnostic question is whether the change has a bounded scope, a defined end state, and a single primary sponsor who can own the organizational change. If the answer is yes, then the Lewin change model modern application is likely to be a strong fit.
When the change involves multiple interdependent projects, shifting priorities, and ambiguous outcomes, a continuous change strategy becomes more appropriate. In those cases, the lewin change sequence still applies at the micro level, but the overall change process must be managed as a portfolio with rolling unfreeze, change, and refreeze stages. This is where frameworks that connect strategy to execution architecture, such as those described in this guide on closing the transformation gap, become essential.
A practical decision rule is to map each initiative on two axes, ambiguity and reversibility. High ambiguity and high reversibility favor iterative experimentation, while low ambiguity and low reversibility favor a structured approach based on the lewin change model. For example, testing a new digital feature with a small user group suits agile sprints, whereas migrating the entire organization to a new payroll process suits a classic unfreeze change and change refreeze arc.
Consultants can also blend the ADKAR model with the Lewin change model modern application to manage both organizational and individual dimensions. The unfreeze stage aligns with building awareness and desire, the change stage aligns with knowledge and ability, and the refreeze stage aligns with reinforcement. This integrated change management approach respects the simplicity of the lewin model while adding the granularity needed for complex organizations.
Finally, the framework should address how to sustain effective change over the long term without promising a permanent refreeze state. Leaders can define a target refreeze stage for each project while acknowledging that future changes will eventually unfreeze that state again. In practice, this means designing governance, metrics, and learning loops that treat each refreeze stage as a platform for the next wave of change rather than a final destination.
How to position Lewin with clients: credibility without nostalgia
Many executives have heard of the lewin change model but suspect it is outdated for modern organizations. Consultants who present the Lewin change model modern application with nuance can strengthen their authority instead of sounding nostalgic. The key is to frame the model as a foundational change theory that still guides specific types of project based change management.
When speaking with clients, start by acknowledging the reality of continuous change and permanent disruption. Then explain that even in such environments, people experience distinct psychological stages that mirror unfreeze, change, and refreeze, especially during high impact changes. This framing respects the client’s context while positioning the lewin model as a practical lens rather than a rigid template.
Next, differentiate between the organization level and the individual level of change. At the organizational level, the lewin change sequence describes how structures, processes, and governance move from one state to another, while at the individual level, models such as the ADKAR model explain how employees build awareness, desire, knowledge, ability, and reinforcement. By showing how these change models complement each other, you demonstrate a structured approach that supports both people and processes.
Clients also respond well to concrete examples that link the unfreeze stage to risk reduction and ROI. For instance, a thorough unfreeze change effort that surfaces hidden resistance can prevent costly delays during the change stage of a system rollout. A disciplined refreeze stage that embeds new behaviors into performance management can protect benefits over the long term and avoid regression to the old status quo.
Finally, be transparent about what the Lewin change model modern application cannot do. It will not manage an entire transformation portfolio on its own, and it does not replace agile methods for exploratory work. Position it instead as a reliable backbone for specific projects within a broader change management ecosystem, where each change stage is chosen deliberately rather than by habit or nostalgia.
Practical design tips: making unfreeze-change-refreeze work in real life
Turning the Lewin change model modern application into daily practice requires disciplined design. Start by defining the current state in concrete terms, including processes, behaviors, metrics, and pain points that justify leaving the status quo. This clarity makes the unfreeze stage tangible for employees and helps leaders align on what exactly must change.
During the change stage, translate high level objectives into specific behaviors and processes that people can practice. For example, if the organization wants more cross functional collaboration, define the new meeting cadences, decision rights, and information flows that will support that behavior. Treat the change stage as a series of experiments within a structured approach, where feedback from employees informs adjustments without derailing the overall project.
The refreeze stage should focus on embedding the new state into systems, incentives, and culture. Update job descriptions, performance metrics, and governance forums so that the new behaviors are reinforced rather than undermined by legacy processes. Think of each refreeze stage as a platform for future continuous improvement, not as a permanent freeze that blocks all future changes.
To keep people engaged, provide visible support throughout the entire change process. This includes clear sponsorship, accessible training, peer coaching, and mechanisms for employees to raise concerns without fear. When organizations treat support as a continuous thread rather than a one time event, the lewin change sequence feels less like a top down imposition and more like a shared project.
Finally, avoid overcomplicating the Lewin change model modern application with unnecessary jargon or tools. A simple visual that shows the unfreeze, change, and refreeze stages, linked to concrete milestones and metrics, often works better than a dense methodology deck. If you offer a free trial of a change management platform or toolkit, position it as a way to operationalize this clarity rather than as a replacement for thoughtful design of each change stage.
FAQ
Is Lewin’s unfreeze-change-refreeze model still relevant for modern organizations?
The Lewin change model remains relevant when the change has a bounded scope, a clear end state, and a defined sponsor. It works particularly well for projects such as system implementations, policy changes, and structural reorganizations where the organization moves from one recognizable state to another. For ongoing transformation, it should be combined with more iterative and agile approaches.
How does Lewin’s model compare with the ADKAR model in practice?
The Lewin change model focuses on the organizational journey from unfreeze to change to refreeze, while the ADKAR model focuses on individual awareness, desire, knowledge, ability, and reinforcement. In practice, many consultants use Lewin to structure the overall change process and ADKAR to manage employee level adoption. The two models are complementary rather than competing.
Can the refreeze stage work in an environment of continuous change?
In continuous change environments, the refreeze stage becomes shorter and more targeted. Organizations use micro refreezes to stabilize specific processes or behaviors long enough to capture value and measure results. These micro refreezes then become the new baseline for the next unfreeze and change cycle.
When should I avoid using a linear change model like Lewin’s?
A linear model is less suitable when the change has high ambiguity, shifting goals, or relies heavily on experimentation and learning. Examples include early stage innovation, exploratory digital products, or cultural shifts without a clear end state. In those cases, iterative and agile approaches should lead, with Lewin’s stages used only as a loose mental model.
How can I explain Lewin’s model to skeptical executives?
With skeptical executives, emphasize that the Lewin change model is not about freezing the organization forever but about stabilizing specific changes long enough to realize benefits. Use concrete examples from their own organization where a clear before and after exists, such as a major system go live. Then position unfreeze, change, and refreeze as a simple way to reduce risk and protect ROI on those investments.