Satir Change Model: The 5 Stages of Performance Through Change

By Brian Tr · Updated Oct 13, 2026

The Satir Change Model describes how a team's performance moves when something disrupts the way it works. It has five stages: late status quo, resistance, chaos, integration and new status quo. Performance usually dips in the middle before it settles higher. Managers use the model to expect that dip, support people through it and avoid abandoning a good change too early.

This guide covers where the model came from, what each stage looks like on a real team, how it compares with Kubler-Ross, Bridges, Lewin, ADKAR and Kotter, and how to use it step by step. You'll also find a template you can copy and a function-by-function set of examples.

Key Facts

• Creator: Virginia Satir (1916-1988), a family therapist described as a key figure in the development of family therapy. The model began in family therapy and was later applied to organizations.
• The five stages: late status quo, resistance (the foreign element arrives), chaos, integration (the transforming idea takes hold), new status quo.
• What it tracks: performance and how people feel, plotted over time. The line falls into chaos, then climbs through integration.
• Software and agile link: Gerald Weinberg introduced the model to many managers in Quality Software Management, Volume 4: Anticipating Change (Dorset House, 1997).
• Best used for: anticipating the dip after a reorganization, a new system or a new way of working, then planning support before it hits.

What is the Satir Change Model?

Think of a line chart. The horizontal axis is time. The vertical axis is how well a person or team performs. The Satir Change Model draws that line as a shape: steady, then a drop, then a climb to a new level.

The core idea is simple. A disruption arrives from outside the group's control. The old way of predicting what happens next stops working, so people struggle. Then someone gets an insight, practice follows, and a new normal forms. The cycle repeats the next time something shakes the system.

Satir built the model to describe how people cope with major, unexpected change. It came out of family therapy, but it applies just as well to teams and organizations. That origin matters. The model is about how people experience disruption, not about project plans or org charts.

Where the model came from

Virginia Satir trained as a social worker and built her career helping families communicate. Psychotherapy.net lists Conjoint Family Therapy (1964) and Peoplemaking (1972) among her best-known books, and notes she served as director of training at the Mental Research Institute in Palo Alto from 1959 to 1966.

The business version came later. Gerald Weinberg, a writer on software and consulting, used the model in Quality Software Management, Volume 4: Anticipating Change, published by Dorset House in 1997. A review of that volume says it introduces the model to describe how people react when a foreign element disrupts their old status quo, especially in the chaos phase.

That software lineage explains why you hear about Satir mostly in agile and engineering circles. Teams adopting a new way of working, such as Kanban or a new release process, recognize the curve immediately. Markus Gärtner, a practitioner writing about the model and Kaizen, notes that even introducing a Kanban board's visualization can act as a foreign element.

The five stages

Sources name the stages a little differently. Some call stage two "resistance," and others "foreign element." Some fold the transforming idea into integration. This guide follows the five-stage version most managers use.

1. Late status quo

Everything feels familiar and balanced. People know their roles, and each day looks like the last. Weinberg describes this as "everything being familiar and in balance," a state Gärtner notes may still carry a hidden cost.

Performance here is stable, but not necessarily good. A sales team can land the same middling result every quarter and call that normal. Some people on the team may already sense that something needs to change, even if nobody says so.

What to do: Notice the stability and ask what it costs. This is the best time to build trust and agree how the team will talk about problems, because those habits will carry you through the next stages.

2. Resistance and the foreign element

A foreign element arrives: new information or an event, from inside or outside the team, that disrupts the routine. It could be a new CEO, an acquisition, a competitor's launch, an AI tool the company has just licensed or a customer who leaves.

Resistance is the natural first response. People ignore the news, blame others, hide from it or argue that it doesn't apply. That's not stubbornness. They're protecting an equilibrium that has worked.

What to do: Name the foreign element plainly, explain the reason for it and say what is not changing. Don't read early resistance as proof the change is wrong. It's usually proof the change is real.

3. Chaos

This is the stage the model is famous for. Old predictions stop working, and people can't yet say what will replace them. In Gärtner's account of the model, people may reject or ignore the change, or revert to older behavior, and their reasoning becomes more emotional.

Performance drops. Relationships strain. Think Insights notes that desperation can produce quick-fix ideas, and that managers should expect productivity to fall. A support team moved to a new ticketing system might see response times slip, handoffs get missed and a few good agents threaten to leave.

What to do: Don't panic and don't pile on targets. Create a safe place to say "this is hard." Our guide to psychological safety covers how. Keep the group connected, and be cautious about the first shiny quick fix.

4. Integration and the transforming idea

Chaos ends with a transforming idea. Gärtner relays Weinberg's description of it as the "AHA!" moment when someone recognizes they have learned something, and says the foreign element starts the chaos while the transforming idea ends it.

The idea might be a new way to structure the work, a clearer picture of why the change helps, or a pilot that simply works. Once it lands, people practice. Per Gärtner, productivity fluctuates in this period and people need slack time to get through it. Setbacks are normal, and Think Insights notes they can send people back into chaos.

What to do: Spot the transforming idea and amplify it. Give people time to practice with real work, not just training slides. Celebrate small wins, and keep the bar for "good enough" realistic while skills are forming.

5. New status quo

The new methods become routine. Predictions hold again and performance levels off, ideally above where it started. The team has a new comfort zone, until the next foreign element starts the cycle again.

What to do: Lock in the habits, update documentation, and ask what you'd do differently next time. And don't mistake this stage for the end. The most useful thing a team can learn is that the cycle will repeat.

Satir Change Model vs other change models

The Satir model draws a performance line. Other models describe emotion, phases, leader actions or individual capability. They answer different questions, so they pair well.

A practical combination: use Lewin or Kotter to plan the change, Satir to forecast the performance dip and set expectations, and ADKAR to coach individuals who are stuck.

How to use the Satir Change Model, step by step

1. Define the foreign element. Write down exactly what is changing, who is affected and when. If you can't state it in two sentences, people won't understand it either.
2. Draw the baseline. Where is performance today? Pick two or three measures you can track: cycle time, error rate, win rate, ticket backlog, engagement scores. Without a baseline you can't tell a dip from drift.
3. Plan for the dip before it arrives. Tell the team honestly that things may get worse before they get better. Leaders who promise instant gains lose credibility the moment chaos hits.
4. Reserve slack. Cut or delay other commitments for the chaos and integration period. A team can't absorb a new system and a normal workload at full speed.
5. Watch for the transforming idea. Ask people in one-on-ones what's starting to make sense. Notice who figures it out first, then ask them to share it.
6. Support practice. Pair people up, run small pilots and make it safe to get things wrong. Treat the first weeks as learning, not as performance review material.
7. Check where you are, don't assume. Teams can sit in different stages at once. Review every two weeks, and expect backward steps.
8. Consolidate and reflect. When the new routine holds, write it down, thank the people who carried it and capture what to do differently next time.

Satir Change Model template

Copy this table into a doc or spreadsheet. Fill one row per team or workstream and update it at each check-in.

Add a column for the transforming idea itself. Writing it down ("pair reviews cut rework on the pilot team") gives you something concrete to spread to other teams.

Examples by business function

These are illustrative scenarios, not real companies.

Take the finance example. In week one, the team continues using the old spreadsheet in secret, which is resistance. In week three, the new tool throws errors nobody understands, and the close slips by two days, which is chaos. Then a junior analyst builds a reconciliation checklist that makes the errors obvious. That checklist is the transforming idea. Within a month the team uses it as standard, and the close runs faster than it did before.

Do's and don'ts

Do:

• Tell people the dip is expected, so a bad week doesn't read as failure.
• Measure performance before, during and after, so you can see the actual shape.
• Protect time for practice during integration.
• Look for the transforming idea and spread it deliberately.
• Remember leaders go through the cycle too. Our guide to adaptive leadership is useful when the challenge has no ready-made answer.
• Treat the next foreign element as certain.

Don't:

• Promise quick wins, then punish the dip.
• Read resistance as insubordination.
• Grab the first quick fix during chaos just to end the discomfort.
• Declare success while people are still practicing.
• Assume every person is in the same stage as the team average.

Limits and criticism

Be straight about what the model can't do. A few honest caveats make you a more credible change leader.

It's a simplification. Real performance doesn't trace a clean curve. Think Insights points out that the line is not thin, so performance fluctuates day to day within its bounds. Your data will be messier than the diagram.

Sources disagree on the stages. Different authors name and group the stages differently, as noted earlier. Pick one version for your team and use it consistently.

It describes, it doesn't prescribe. The model won't tell you which change to make. If the change is badly designed, the dip may never recover, and a better plan is the fix, not more patience. Pair it with a case for change, such as the Beckhard-Harris change formula.

It can feel fatalistic. If a leader treats chaos as inevitable, they may stop trying to shorten it. The dip is common, but its depth and length depend on preparation, support and how clear the transforming idea is.

Evidence for the business version is largely practitioner experience. It has been a durable teaching tool in software and consulting, but treat it as a lens for conversation, not a forecast with guaranteed timing.

Common mistakes

Starting measurement after the change. Without a baseline, nobody can show whether the new state is better.

Skipping the late status quo. Teams that never examine why the old way worked don't know what they're giving up.

Calling it done in chaos. Pulling support the moment people start using the new system leaves them stranded in the hardest stretch.

Treating the transforming idea as an announcement. It's an insight people reach by doing the work. You can set up the conditions, but you can't hand it down.

Ignoring the next cycle. Once a new status quo forms, the next foreign element is already on its way. Teams that build change habits handle it better.