Lewin’s 3-Stage Change Model: Practical Examples from Business and Project Management
Lewin’s 3-Stage Change Model provides a straightforward framework for understanding how organizations move from established working practices to a new operating state. Its three stages, unfreeze, change, and refreeze, help managers identify what must happen before implementation, during the transition, and after a new process or system is introduced.
The model is particularly useful in project management because delivering a solution does not guarantee that people will use it. A new project management platform can be technically operational while teams continue maintaining separate spreadsheets. A redesigned approval process can be documented while employees still follow the previous procedure.
These situations reveal the distinction between delivering change and achieving it. Lewin’s framework encourages project managers to address the conditions that make change possible, support people through implementation, and establish the systems that sustain new behaviors.
What Is Lewin’s 3-Stage Change Model?
Developed from the work of social psychologist Kurt Lewin, the model describes organizational change as a transition from an existing state to a different, more stable state. The familiar framework consists of unfreeze, change, and refreeze, although Lewin’s original terminology is commonly associated with unfreezing, moving, and freezing.
The underlying idea is that established behaviors persist because organizational routines, expectations, incentives, and relationships reinforce them. Introducing a new process requires more than announcing a decision. The forces maintaining current behavior must be addressed, people must learn new ways of working, and the organization must reinforce the resulting changes.
The framework is a useful way to structure change management, but it is not a detailed project delivery methodology. It does not independently prescribe a stakeholder engagement plan, training curriculum, implementation schedule, or benefits realization process. Project managers must develop those activities around the model's three stages.
Stage 1: Unfreeze
Unfreezing prepares the organization to move away from existing practices. Managers establish why change is necessary, examine the problems with the current state, and address the concerns that could prevent adoption.
This stage should involve more than communicating a compelling vision. Leaders need to understand why employees may prefer existing processes, including familiarity, perceived job security, workload pressures, and concerns about losing control over their work.
For example, a department introducing standardized project reporting might encounter resistance from managers who believe the existing reports provide greater flexibility. Simply instructing them to use a new template is unlikely to resolve their concerns. Demonstrating how inconsistent reporting delays portfolio decisions, involving managers in designing the new format, and explaining which reporting requirements will disappear can create stronger readiness for change.
The objective is not to eliminate all resistance. It is to understand the reasons behind it and establish conditions in which people can participate constructively.
Stage 2: Change
The change stage is where the organization introduces new processes, systems, responsibilities, or behaviors. People begin working differently, encounter unfamiliar situations, and develop the skills required to operate in the new environment.
Implementation needs clear ownership, adequate resources, training, communication, and opportunities to identify problems. Project managers should avoid assuming that distributing instructions or providing a single training session guarantees competence.
A phased rollout can be useful when the organization needs to test assumptions before committing to a wider implementation. Pilot groups can identify workflow problems, expose missing requirements, and provide feedback before the new approach becomes standard.
Progress should be assessed using both delivery measures and adoption indicators. A system may meet its technical acceptance criteria while employees struggle to complete routine tasks. Monitoring usage, task completion, error rates, support requests, and user feedback can reveal whether the change is working as intended.
Stage 3: Refreeze
Refreezing embeds the new way of working into normal organizational operations. The objective is to reduce the likelihood that employees will revert to previous behaviors once the implementation team moves on or management attention shifts elsewhere.
This requires more than celebrating a successful launch. Organizations may need to update standard operating procedures, role descriptions, approval rules, training materials, performance measures, and management reporting.
Operational ownership is especially important. If the project team remains the only group responsible for resolving problems, the change may weaken when that team disbands. A named business owner, defined support arrangements, and ongoing performance monitoring help establish accountability.
Refreezing does not mean that an organization must resist all future change. In a dynamic environment, it is better understood as establishing a sufficiently stable operating baseline while retaining the ability to improve it.
Practical Examples of Lewin’s Model in Business and Project Management
The following examples are hypothetical scenarios illustrating how managers can apply the framework. They are not presented as documented company case studies.
Example 1: Implementing a Project Management Software Platform
A business decides to replace disconnected spreadsheets with a centralized project management platform. The software has been selected, but successful implementation depends on whether project managers, team members, and executives consistently use it.
During unfreeze, the project sponsor documents the problems with existing reporting, including duplicated data entry, inconsistent status definitions, and delayed escalation of project risks. Representatives from affected teams help identify workflow requirements and concerns about the proposed platform.
During change, the implementation team configures the platform, migrates relevant project data, trains users, and introduces the system to a pilot group. Feedback identifies confusing status fields and unnecessary reporting steps, which are corrected before the wider rollout.
During refreeze, the organization establishes the platform as the authoritative source of project status. Reporting procedures are updated, portfolio reviews use its data, and business owners monitor adoption and data quality.
The central lesson is that software deployment is a delivery milestone, not proof of business adoption. The change becomes sustainable when the platform is incorporated into the decisions, routines, and accountability structures of the organization.
Example 2: Standardizing Project Governance
A PMO discovers that different departments use inconsistent project approval criteria. Some projects begin without approved business cases, while others lack clear ownership of risks and benefits.
During unfreeze, the PMO presents examples of inconsistent decisions and explains how unclear approval requirements undermine portfolio prioritization. Department leaders help identify where the existing governance arrangements create unnecessary delays.
During change, the organization introduces standardized approval gates, decision rights, escalation thresholds, and reporting requirements. A pilot involving selected projects tests whether the new controls improve decision quality without creating disproportionate administrative work.
During refreeze, the new governance requirements become part of the project lifecycle. Templates are updated, approval responsibilities are documented, and periodic assurance reviews assess compliance and the quality of decisions.
The important distinction is between publishing a governance framework and changing management behavior. Governance becomes embedded when decision-makers consistently apply the agreed criteria and the organization addresses recurring exceptions.
Example 3: Introducing a New Business Process
Consider a company that wants to replace email-based purchase approvals with a structured digital workflow.
During unfreeze, managers examine approval delays, lost requests, and the difficulty of identifying outstanding decisions. Employees explain why they currently rely on email, including concerns about system access and the need to handle urgent exceptions.
During change, the organization configures the workflow, tests approval routes, trains employees, and introduces the process to selected departments. The project team monitors rejected submissions, processing times, and requests requiring manual intervention.
During refreeze, the digital workflow becomes the standard route for purchase approvals. Procedures clarify exception handling, managers receive regular performance reports, and support teams take responsibility for operational issues.
This example highlights a frequent implementation risk: designing a process around the ideal workflow while ignoring legitimate exceptions. Sustainable adoption requires a clear standard process and controlled mechanisms for handling situations that fall outside it.
How to Apply Lewin’s Model to a Change Project
The model becomes more useful when each stage is connected to evidence that the organization is ready to progress. The following table translates the framework into practical project management decisions.
Stage | Key management activities | Evidence of progress | Common failure |
Unfreeze | Analyze the current state, establish the case for change, engage stakeholders, identify resistance, and clarify the intended outcomes. | Stakeholders understand the rationale, major concerns have owners, and the organization has agreed on the problem to solve. | Leaders announce the change before addressing operational concerns or explaining why existing practices are inadequate. |
Change | Implement the solution, provide training, test workflows, communicate progress, and resolve implementation problems. | Users can perform required tasks, adoption measures improve, and operational issues are being resolved. | The solution is delivered without sufficient support, user feedback, or time to develop competence. |
Refreeze | Update procedures, assign operational ownership, reinforce expectations, monitor performance, and maintain support arrangements. | The new process is consistently used, operational performance is stable, and responsibilities have transferred to the appropriate owners. | The project closes immediately after launch, allowing employees to revert to previous practices. |
Three observations follow from this comparison.
First, progression should depend on evidence rather than the calendar alone. A project may have completed its communications activities without resolving the concerns preventing adoption. Likewise, a scheduled launch date does not establish that users are ready to operate the new system.
Second, the stages require different management responses. Unfreeze focuses on readiness and the forces maintaining current behavior. Change focuses on implementation and learning. Refreeze focuses on reinforcement, operational accountability, and sustained performance.
Third, the final stage needs explicit ownership. Without a business owner, baseline performance measures, and an agreed approach to monitoring adoption, the organization may be unable to distinguish lasting improvement from a temporary increase in compliance.
Limitations and When to Use an Alternative
Lewin’s model is valuable because it offers a clear way to think about organizational change. Its simplicity, however, can become a weakness when managers interpret it as a rigid sequence suitable for every situation.
Large transformations may involve multiple workstreams progressing at different speeds. One department may be stabilizing a new process while another is still preparing for implementation. Regulatory changes, market shifts, or new technical requirements may also force organizations to revise a recently introduced operating model.
In these circumstances, the three stages are better used as a diagnostic framework than as a strict project schedule. Managers can ask whether affected groups are ready, whether implementation is supported, and whether new practices are being sustained without requiring every part of the organization to occupy the same stage simultaneously.
The model also provides limited detail about how to manage individual reactions, build a guiding coalition, or coordinate a complex transformation. More detailed change management approaches may be appropriate when these requirements dominate the work.
For project managers, the decision is not whether Lewin’s model is universally superior. It is whether its three-stage structure addresses the principal risk in the change being undertaken. For a contained process redesign, system rollout, or governance improvement, it can provide a useful organizing framework. For a prolonged transformation involving continuous strategic and organizational adaptation, it may need to be supplemented with more detailed methods.
Frequently Asked Questions
1. What are the three stages of Lewin’s change model?
The stages are unfreeze, change, and refreeze. They represent preparing people for change, implementing new ways of working, and reinforcing those practices so they become part of normal operations.
2. How can project managers measure whether Lewin’s model is working?
Measure readiness, adoption, and sustained performance separately. Useful indicators include training completion, active system usage, process compliance, error rates, cycle times, and whether business benefits continue after project closure.
3. What is the main weakness of Lewin’s 3-stage change model?
Its simplicity can encourage an overly linear interpretation of change. Complex organizations may need overlapping activities, repeated transitions, and additional methods to manage individual responses, organizational politics, and continuous adaptation.
Conclusion: Lewin’s 3-Stage Change Model: Practical Examples from Business and Project Management
Lewin’s 3-Stage Change Model offers project managers a useful framework for connecting organizational readiness, implementation, and long-term adoption. Its greatest value lies in exposing the work that can be overlooked when change is treated primarily as a technical delivery exercise.
The three stages help managers ask different but connected questions: have we established why change is necessary, can people operate effectively in the new environment, and have we created the conditions needed to sustain the change?
Applying the framework effectively requires more than assigning activities to three headings. Managers need evidence of readiness, meaningful support during implementation, and clear operational ownership after delivery. They must also recognize that different teams may progress at different speeds and that changing circumstances can require another cycle of adjustment.
Over the next two years, organizations are likely to continue introducing new digital systems, automation, and AI-enabled workflows. These developments will make the distinction between implementation and adoption increasingly relevant. Lewin’s model can help managers structure that work, provided they use it flexibly and supplement it where more detailed change management capabilities are required.
The ultimate measure of success is not whether a project launched on time. It is whether the intended change produces sustained improvements in how the organization operates.
