Satir change model

Virginia Satir's model came from family therapy and was adapted for organizations, notably by Gerald Weinberg. It describes how a system moves from one stable state to another, and it is the best available account of the performance dip.

Evidence: Weak as a model, well documented as a phenomenon. The five-stage structure has no formal validation. The phenomenon it describes — a substantial temporary performance drop after a competence-disrupting change — is repeatedly documented, most clearly in electronic health record implementations, where clinician productivity declines measurably for weeks to months post go-live. Trust the dip; treat the stage names as vocabulary.

Use when: leading a team through a change that temporarily makes them worse at their jobs — new tooling, new process, new structure, new skills.

Do not use when: the change requires no new competence.

The five stages

1. Late status quo. Familiar, predictable performance. Not necessarily good performance — merely known. People have a working model of how things go.

2. Foreign element. Something arrives that the existing model cannot accommodate: a new manager, a new system, a merger, a new regulation, a crisis. First reaction is to reject, ignore, or minimize it. Denial here is a defense of the working model, not stupidity.

3. Chaos. The old model no longer works and no new model exists yet. Performance drops, sometimes below the original baseline. Anxiety is high, behavior is erratic, people revert to old habits under pressure. This is normal and necessary — it is not a sign the change was wrong.

4. Transforming idea. An insight that makes the new situation make sense. "Oh — this is how it fits together." It usually arrives from inside the group rather than from a leader's explanation, and it cannot be scheduled.

5. Practice and integration. The new model is tried, refined, and made automatic. Performance climbs, typically above the old status quo, but only after deliberate practice.

6. New status quo. Stable again, at a higher level, until the next foreign element.

Why the chaos stage matters most

Three predictable errors occur in chaos:

• Abandonment. Leadership sees the dip, concludes the change failed, and reverts — one week before the transforming idea. The organization learns that changes get reversed, which raises resistance to the next one.
• Escalation. Leadership sees the dip and adds pressure, targets, or monitoring. This lengthens chaos by consuming the capacity needed to find the transforming idea.
• Stacking. A second foreign element is introduced during chaos, because the calendar said so. Two chaoses do not resolve faster than one.

The correct response to chaos: reduce other demands, increase psychological safety, shorten feedback loops, and say publicly that the dip was expected and has an end.

Accelerating the transforming idea

• Give people time and permission to experiment, with a low cost of failure.
• Pair people with someone who has already made the transition.
• Surface partial insights early and often — retrospectives, demos, short huddles — because the transforming idea usually appears first in one person's workaround.
• Protect slack. Insight does not happen at 100% utilization.

Examples by audience

• Health care: an electronic health record go-live produces a documented and substantial productivity drop for weeks to months. Organizations that plan reduced clinic lists during chaos recover faster than those that maintain full throughput and burn out their clinicians.

• Software: adopting a new language, framework, or architecture makes an experienced team temporarily junior. The transforming idea is usually a specific worked example in their own codebase, not documentation.

• Executive: an executive who changes operating model and simultaneously raises targets has stacked a second foreign element onto chaos. Expect a longer and deeper dip, and expect to be told everything is fine.

Limitations

• Descriptive rather than predictive; the timing of the transforming idea cannot be forecast.
• No formal empirical validation as an organizational model.
• Says little about structure, incentives, or strategy.

See also

• bridges-transition-model
• psychological-safety
• Gerald Weinberg, Quality Software Management, Vol. 4: Anticipating Change.