Kurt Lewin's three-stage model — unfreeze, change, refreeze — is the foundation of the change management field. Almost every later model is an elaboration of it.

Evidence: Weak. The three-step formulation was substantially simplified after Lewin's death, and has never been tested as a model. Later scholarship disputes how much of it is his. The unfreeze concept is supported indirectly — disconfirmation plus safety produces learning where disconfirmation alone produces defensiveness — and the institutionalization requirement is supported by the reliability with which unreinforced changes decay. Foundational, not evidential.

Use when: you need the simplest correct mental model of change, or when you want to diagnose which stage a stalled effort is stuck in.

Do not use when: you need operational detail. It is a frame, not a method.

The three stages

  1. Unfreeze: create readiness. Disconfirm the current state — show that the status quo is no longer viable — while providing enough psychological safety that people can face the disconfirmation without defending. Schein's later refinement: disconfirmation alone produces denial; disconfirmation plus safety produces learning.

  2. Change (transition): the movement itself. New behaviors are tried, competence is temporarily low, and performance usually dips. This is the stage most programs under-resource, because it looks like failure while it is working. See satir-change-model.

  3. Refreeze: stabilize the new state so it becomes the default. Update policies, metrics, incentives, onboarding, and stories. Without refreeze the system reverts, usually within two quarters, and the reversion is then remembered as proof that change is impossible here.

The unfreeze problem

Most change efforts begin at stage 2. A new process is announced with no disconfirming evidence and no safety, and the organization treats it as noise. Unfreezing is the work of establishing that the current state costs something — with data the audience already trusts, not with slides.

The complementary error is disconfirmation without safety: relentless bad news, public blame, or a burning-platform speech that makes people protect themselves rather than change.

Refreeze in a world that never freezes

The common modern criticism — organizations never stabilize, so "refreeze" is obsolete — is partly fair and mostly misapplied. The underlying requirement survives: a new behavior must be made cheaper than the old one, or it decays. Read "refreeze" as institutionalize: the change is complete when a new person joining next month does the new thing without being told.

Lewin's own operational tool for stage 1. See force-field-analysis. His key claim: reduce restraining forces rather than increasing driving forces, because added driving force raises tension and provokes counter-pressure.

Examples by audience

  • Health care: unfreezing a ward on a hand-hygiene or handover change works when the team sees its own audit data, not national averages. Refreeze happens when the behavior enters the ward round checklist and the induction pack for rotating junior staff.

  • Software: unfreeze with the team's own delivery telemetry — lead time, change failure rate. Refreeze by encoding the change in the pipeline, the templates, and the definition of done, so the new way is the path of least resistance. See dora-metrics.

  • Executive: executives typically unfreeze themselves months before the organization, then mistake their own readiness for shared readiness. The organization is at stage 0 when the executive is at stage 3.

Limitations

  • Treats organizations as more stable and more unitary than they are.
  • Implies a linear, planned sequence; real change is iterative and contested.
  • Later scholarship disputes how much of the simplified "three-step model" is Lewin's own formulation versus a posthumous simplification.
  • Silent on individual psychology; pair with bridges-transition-model.

See also

Organizational Development — a comprehensive practitioner's guide to OD for health care professionals, software engineers, and senior executives. Every framework says what the evidence is, and where it is weak.

Source and contributions: github.com/organizational-development. Built with the Lily Design System™.