Lewin's Change Model

Theory & origin

Kurt Lewin published the three-stage model in 1947, out of his field theory: behavior is an equilibrium held in place by driving forces pushing for change and restraining forces resisting it, which is also where his force-field analysis comes from. Unfreezing destabilizes that equilibrium, and Edgar Schein's elaboration explains how: disconfirming data creates survival anxiety, but movement only happens when psychological safety keeps learning anxiety smaller than the urgency. The change phase is when new behaviors get tried and coached while the system can still flow. Refreezing anchors the new pattern in systems, incentives, and routines, because an unanchored change reverts, always. The standard critique is that the model is too linear for an era of continuous change, and that nothing ever refreezes anymore. The fair reading is that Lewin froze the new pattern, not the organization's ability to change again, and that his successors kept his physics: Kotter's eight steps are an elaborated Lewin, with steps one to four as unfreezing, five to seven as movement, and eight as refreezing. The most useful corollary is also the least followed: removing restraining forces beats piling on driving forces, which just raises the tension a frozen system eventually snaps back with.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

How a consultant runs it

1. 01 Run the force-field analysis first: list and weight the driving and restraining forces. The map tells you whether to push or unblock, and unblocking is almost always cheaper.
2. 02 Unfreeze with disconfirming data people cannot argue with, paired with enough psychological safety that the data produces movement instead of denial.
3. 03 Prefer removing restraining forces over adding driving forces. More pressure on a frozen system raises the tension it snaps back with.
4. 04 Time-box the fluid phase. A system held unfrozen too long breeds anxiety, and people re-freeze themselves into whatever habits form first.
5. 05 Refreeze deliberately: wire the new behavior into systems, incentives, and routines, then stop announcing the change and let the new normal get boring.

Worked example

A bank replaces its teller workflow. The first attempt announces the new system on a Monday and calls it done: within six weeks, 70% of branches have drifted back to workarounds that mimic the old screens. The Lewin rerun does the boring physics. Unfreeze: branch heads see their own error and queue-time data, and hear the honest line, the old flow is being retired, and here is what stays the same for you. Change: two pilot regions run both flows for a month with floor walkers and a daily fix list. Refreeze: the old screens go dark on a named date, the workarounds are disabled, KPIs and incentives repoint at the new flow, and the fix list keeps running for a quarter. A year later the new workflow is just how tellers work, which is the only success metric Lewin recognizes.

Common pitfalls

1. 01 Skipping unfreeze and announcing change into a frozen system, which produces compliance theater and drift-back
2. 02 Adding driving forces instead of removing restraining ones, which raises tension instead of creating movement
3. 03 Holding the organization fluid indefinitely: perpetual reorgs teach people to wait every change out
4. 04 Declaring victory at go-live. Refreeze is systems and incentives, not a launch email.
5. 05 Reading refreeze as rigidity. Lewin froze the new pattern, not the ability to change again.

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.