Lewin's Change Model

Lewin's Change Model: Unfreeze-Change-Refreeze

Kurt Lewin 1947 Medium Complexity

Lewin's Change Model is the foundational 3-stage framework for understanding change: Unfreeze (prepare), Change (transition), and Refreeze (stabilize).

What Is It?

Kurt Lewin's Change Model, developed in 1947, is the grandfather of all change management frameworks. Using the metaphor of changing a block of ice, Lewin explained that organizations must first unfreeze their current state before change can occur.

Unfreeze: Prepare for change by creating awareness, challenging the status quo, and building motivation to change. Change: The transition period where new processes, behaviors, and ways of thinking are implemented. Refreeze: Stabilize the new state by embedding new norms and preventing regression.

Lewin also developed Force Field Analysis, which maps driving forces against restraining forces. Modern frameworks like Kotter's 8-Step and ADKAR build on Lewin's foundational insights.

Lewin's 3-stage model and Force Field Analysis
Lewin's three stages: Unfreeze, Change, Refreeze

Quick Reference

Complexity
Medium (5/10)
Time to Decision
3-6 months
Data Required
Low
Team Size
3-20
Objectivity
High
Learning Curve
1-2 weeks

When to Use

  • Understanding change dynamics conceptually
  • Teaching change management principles
  • Smaller-scale organizational changes
  • Foundation before applying detailed models
  • Force Field Analysis for resistance mapping

When NOT to Use

  • Need detailed implementation steps (use Kotter's 8-Step)
  • Complex enterprise transformation
  • Need individual-level guidance (use ADKAR)
  • Rapid, iterative change environments

Key Strengths

  • Simple: Easy to understand and remember
  • Foundational: Core concepts underpin all models
  • Universal: Applies to any change context
  • Force Field: Powerful diagnostic tool

Key Weaknesses

  • Oversimplifies complex change
  • Linear model may miss iterative nature
  • Less actionable than modern frameworks
  • "Refreeze" may not fit agile environments

How It Works

1 Primary InputCurrent state assessment, change drivers, resistance factors
2 Data You NeedStakeholder readiness, driving and restraining forces
3 Primary OutputChange plan with stages, Force Field Analysis