Satir Change Model

1. What Is Satir Change Model?

The Satir Change Model is a people-centered framework that describes the typical emotional and performance dynamics individuals and groups experience during change. It maps how a “foreign element” (the trigger for change) disrupts an existing status quo, produces resistance and chaos, then—through a transforming idea and practice—leads to a higher-performing new status quo.

Within the Organization function, it sits in Change Management & Transformation frameworks. Consultants and executives use it to anticipate the “J‑curve” of performance, normalize reactions to disruption, time interventions (coaching, training, support), and sustain momentum through the messy middle of change.

In plain language: expect a dip before improvement. People initially resist or feel disoriented; with the right ideas, support, and practice, they regain confidence and performance surpasses the starting point. The model helps leaders respond constructively at each stage.

2. Origin and Background

The model originates in the work of Virginia Satir, a pioneering family therapist (1916–1988), who observed common patterns in how individuals and families respond to disruptive events and adapt over time. Those insights were later adapted for organizational contexts, especially in systems thinking and software/technology communities in the 1990s and 2000s (e.g., via consulting literature that applied Satir’s curve to organizational change and learning).

Why it was created (and adapted): to make the human dynamics of change visible and predictable enough that leaders can support healthier transitions—reducing unproductive resistance, shortening time in chaos, and accelerating learning and integration.

How it spread: through organizational development practice, agile and lean communities, and executive education. The “Satir curve” is commonly used alongside programmatic frameworks (Lewin, Kotter, ADKAR) as a diagnostic of emotional and performance states during change.

3. How the Satir Change Model Works

The model depicts a sequence of phases people and groups tend to traverse when confronted with a significant change. While labels vary slightly by source, the logic is consistent: disruption → destabilization → discovery → practice → stabilization at a higher level.

Typical phases

• Late Status Quo
  • What it is: The pre‑change state where routines are familiar and performance is relatively stable. Issues may be present but are normalized.
  • Leader implication: Make the case for change while acknowledging what the status quo achieved; avoid dismissing existing practices that people identify with.
• Foreign Element
  • What it is: The trigger disrupting the status quo—new strategy, technology, regulation, competitor move, merger, leadership change.
  • Leader implication: Communicate clearly what’s changing and why; expect initial questions and pushback.
• Resistance
  • What it is: Natural responses ranging from skepticism to fear or anger as people anticipate losses (autonomy, competence, identity).
  • Leader implication: Normalize resistance; listen, address WIIFM (what’s in it for me), and reduce perceived losses (e.g., reskilling, fair transitions). Avoid labeling people as “blockers” for predictable reactions.
• Chaos
  • What it is: The performance dip. Old routines no longer work; new ones aren’t yet competent. Emotions range from confusion to fatigue; errors and cycle times can worsen.
  • Leader implication: Increase support and communication cadence; simplify priorities; provide coaching and rapid issue resolution. Expect a temporary productivity trough and plan for it.
• Transforming Idea
  • What it is: An insight, practice, or design that makes the new way “click” (e.g., a better workflow, a template, a mental model). It reduces anxiety and raises efficacy.
  • Leader implication: Invest in pilots and learning loops to surface and spread these ideas; highlight credible early adopters.
• Practice & Integration
  • What it is: Repetition builds competence; processes stabilize; confidence grows. Performance recovers and starts to exceed the baseline.
  • Leader implication: Provide time to practice; embed job aids, coaching, SOPs; align KPIs and incentives to reinforce the new behaviors.
• New Status Quo (at a higher level)
  • What it is: The change is internalized; the new way feels normal; performance plateaus at an improved level relative to the start.
  • Leader implication: Celebrate, codify lessons, and maintain continuous improvement so the new plateau doesn’t become complacency.

The performance–emotion curve

• Most depictions show performance on the vertical axis and time on the horizontal axis—forming a curve: stable baseline → dip after disruption → climb after transforming ideas and practice → new, higher plateau.
• Emotional states broadly track the curve: comfort → anxiety/denial → confusion/frustration → curiosity/hope → confidence/engagement.

Why it’s useful for executives

• Predictable pattern: Anticipate where pushback and dips occur; stage support accordingly.
• Intervention timing: Use different tools in each phase—e.g., acknowledgment and clarity in Resistance, pilots and coaching in Chaos, reinforcement in Integration.
• Communication framing: Normalize the dip; prevent overreaction (e.g., abandoning a good strategy due to a predictable trough).

4. When to Use the Satir Change Model

Most helpful when:

• Your change will disrupt routines and require people to unlearn–relearn (new systems, operating model, culture shifts).
• You need to prepare stakeholders and boards for an expected performance dip—and avoid premature course corrections.
• You’re orchestrating a multi‑wave rollout and want to shorten time in chaos by extracting and spreading transforming ideas quickly.

Especially powerful for: ERP/CRM implementations, agile transformations, shared‑services migrations, restructurings, and regulatory process overhauls where skill acquisition and identity shifts are material.

Use with caution when:

• Change is minor and reversible (small feature updates); a heavy transition lens may add overhead.
• Leaders might mistake the model for a program plan; it’s a human dynamics guide, not a substitute for project management or operating model design.
• There is no clear target behavior; pair with discovery methods (design thinking, agile) to define “transforming ideas.”

Current practice: Organizations pair Satir with Kotter (leadership sequence), ADKAR (individual adoption), and agile/lean (experimentation). Satir provides the emotional/performance map to orchestrate timing and expectations.

5. How to Apply the Satir Change Model: Step‑by‑Step

1. Define the change and articulate the case

   Describe what’s changing (processes, roles, systems) and why now—link to customer, risk, economics. Identify expected benefits and the known “foreign elements” (e.g., regulatory deadlines, platform end‑of‑life). Set measurable success criteria (adoption, proficiency, performance).

2. Map stakeholders and likely phase progression

   Segment by role and exposure (frontline users, managers, support teams, customers). For each, estimate where and when they’ll hit Resistance, Chaos, and Integration. Identify high‑influence groups likely to experience deeper losses (identity, autonomy) and prioritize support.

3. Design phase‑appropriate interventions

   Build a simple playbook aligned to phases:

   • Late Status Quo → Foreign Element: Sponsor messaging, town halls, customer stories, clear “why now,” and high‑level roadmap.
   • Resistance: Two‑way forums, manager 1:1s, WIIFM tailoring, mitigation of losses (reskilling paths), quick myth‑busting FAQs.
   • Chaos: Pilots, “floor walkers,” hotlines, simplified priorities, temporary workload relief, daily huddles, 24–72h issue SLAs.
   • Transforming Idea: Capture/scale what works (templates, scripts, UX tweaks); recognize early adopters.
   • Practice & Integration: Role‑based coaching, job aids, SOPs, metrics and incentives aligned to the new way.
   • New Status Quo: Celebrate, codify, and transition to continuous improvement.
4. Plan for the dip (protect the business)

   Quantify the likely productivity trough and duration by group. Adjust targets, staffing, and cutover plans (e.g., parallel runs, phased rollouts). Communicate proactively to boards and customers; define thresholds that trigger extra support versus true course corrections.

5. Run discovery to surface transforming ideas fast

   Set up pilots with rapid feedback loops. Use frontline co‑design to uncover practical solutions (workflow changes, checklists, UI improvements). Create a lightweight mechanism to evaluate, package, and broadcast the transforming ideas enterprise‑wide.

6. Enable practice and integration

   Invest in role‑based training close to go‑live, hands‑on labs, peer coaching, and time for practice. Decommission legacy tools to prevent backsliding. Update governance, KPIs, and incentives to reinforce the new behaviors; make the new way the path of least resistance.

7. Measure the curve and adapt

   Track sentiment (pulse surveys), adoption (usage/proficiency), and performance (cycle time, quality, customer metrics) weekly during chaos and monthly thereafter. Visualize the curve; escalate hotspots where the trough is deeper/longer than expected; deploy additional coaching or redesign work if needed.

8. Institutionalize lessons for future waves

   After stabilization, hold retrospectives to capture timing, support effectiveness, and the highest‑impact transforming ideas. Create reusable playbooks and a community of practice to shorten future dips.

6. Example: Satir Model in Action

Context: A $1.4B medical devices company migrated global sales and service to a new CRM and CPQ platform, alongside redesigned pricing governance. A prior rollout had faltered due to extended chaos—sales reverted to spreadsheets, approval cycle times ballooned, and morale dipped.

Approach using Satir:

• Late Status Quo/Foreign Element: The CRO and CFO jointly presented customer and leakage data, explained regulatory and margin risks, and set a public target for quote cycle time and price realization. A staged rollout plan (by region) was shared.
• Resistance: Managers held 1:1s to surface fears (quota risk, loss of autonomy). A reskilling program for deal modeling and a clear exception process mitigated perceived losses. WIIFM messaging emphasized faster approvals and fewer rework loops.
• Chaos: During first‑wave go‑live, “floor walkers” (power users) supported reps; a 48‑hour SLA addressed CPQ defects. Leadership paused non‑critical initiatives, simplified targets, and ran daily huddles. Performance dip (quote cycle time +35%) was anticipated and communicated in advance.
• Transforming Ideas: Two practices emerged: a deal‑qualification checklist that cut iterations by 25% and a CPQ template for standard configurations covering 60% of quotes. These were packaged and deployed to all regions within two weeks.
• Practice & Integration: Reps received quick‑reference guides; managers coached weekly using pipeline reviews focused on cycle time and price realization. Old spreadsheet calculators were removed from shared drives at week 6, with controlled exceptions.
• New Status Quo: After 10 weeks, cycle time fell 28% below baseline; price realization improved by 140 bps. The curve for later regions showed a shallower, shorter dip due to earlier transforming ideas and playbooks.

Outcomes (4 months): 92% CRM/CPQ adoption, 30% reduction in approval touchpoints, +8‑point sales NPS (internal enablement survey). Executive updates used the Satir curve to show expected vs. actual dips, maintaining board confidence through the transition.

7. Strengths and Limitations

Strengths

• Makes the human curve explicit: Normalizes resistance and the performance dip, reducing panic and blame.
• Practical timing guide: Helps leaders match interventions to phase—acknowledgment during resistance, support and experimentation in chaos, reinforcement in integration.
• Complements program frameworks: Works well with Kotter, Lewin, and ADKAR; adds an emotional/performance lens they often assume.
• Improves stakeholder management: Useful for setting board/customer expectations and avoiding premature rollbacks.

Limitations

• Not a plan: It doesn’t specify governance, workplans, or benefits tracking—you must layer those on.
• Risk of determinism: Treating the curve as fate can excuse poor design or support. A deep/long dip may signal fixable issues, not “inevitability.”
• Subjectivity: Assigning teams to phases relies on judgment; triangulate with data (usage, quality, cycle times) and direct feedback.
• Variance across groups: Different functions and geographies will sit in different phases; one-size interventions may misfire.

8. Common Pitfalls (and How to Avoid Them)

• Dismissing the old status quo

  What goes wrong: People feel disrespected; resistance hardens.

  How to avoid: Acknowledge past success; explain why evolution is necessary now; separate respect for history from the need to change.

• Under‑resourcing the chaos phase

  What goes wrong: Productivity collapses; workarounds entrench; morale drops.

  How to avoid: Provide power users, hotlines, reduced workload, tight issue SLAs, and daily huddles for rapid learning and fix.

• No mechanism to capture transforming ideas

  What goes wrong: Good practices stay local; later waves repeat early mistakes.

  How to avoid: Run structured pilots and retros; package and broadcast checklists/templates rapidly; recognize contributors.

• Overpromising a “no dip” change

  What goes wrong: Trust erodes when the inevitable dip occurs.

  How to avoid: Set realistic expectations; show the curve; commit to shortening and shallowing the dip, not eliminating it.

• Leaving legacy tools accessible

  What goes wrong: People revert under pressure; adoption stalls.

  How to avoid: Decommission or sandbox legacy paths with clear exceptions and timelines; make the new way the easiest path.

• Uniform messaging across heterogeneous groups

  What goes wrong: Messages miss specific losses; resistance persists.

  How to avoid: Tailor WIIFM and support by role and phase; equip managers to localize messages.

• Declaring “new status quo” too early

  What goes wrong: Without reinforcement, behaviors regress.

  How to avoid: Anchor with KPIs, incentives, SOPs, and ongoing coaching; keep measuring for quarters after go‑live.

9. How the Satir Model Relates to Other Frameworks

• Lewin Three‑Stage (Unfreeze–Change–Refreeze): Satir provides a finer‑grained view within Lewin’s phases—Resistance and Chaos align with Unfreeze/Change; Transforming Idea and Integration align with late Change/Refreeze.
• Kotter’s 8 Steps: Use Satir to set expectations during steps 5–7 (remove barriers, short‑term wins, sustain acceleration) when chaos and learning are most intense.
• Prosci ADKAR: Satir’s phases help diagnose which ADKAR elements to emphasize: Desire during Resistance; Knowledge and Ability during Chaos and Integration; Reinforcement at New Status Quo.
• Bridges Transition Model: Both are human‑centric. Satir emphasizes performance and transforming ideas; Bridges emphasizes psychological phases (Ending, Neutral Zone, New Beginning). They reinforce each other.
• Agile/Lean: Agile practices are ideal for Chaos → Transforming Idea → Integration (short cycles, experiments, retros). Satir helps explain why agile learning loops matter.
• Benefits/Value Realization: Use Satir’s curve to predict timing of benefits (dip then rise), reduce misinterpretation of early metrics, and set stage‑gate expectations.

10. Key Takeaways

• The Satir Change Model maps the emotional and performance journey of change—expect a dip (chaos) before improvement.
• Match interventions to phase: acknowledge and clarify in Resistance; over‑invest in support and learning loops in Chaos; reinforce during Integration to lock in the new status quo.
• Capture and spread transforming ideas fast to shorten and shallow the dip across waves.
• Use Satir to set realistic expectations with boards and teams; avoid abandoning sound strategies due to predictable early dips.
• Satir complements Kotter, Lewin, ADKAR, and agile by providing the human performance lens they often assume.

11. FAQs About the Satir Change Model

Is the Satir model only about emotions?
No. It links emotions to observable performance patterns—stable baseline, dip in chaos, then improvement through transforming ideas and practice. That linkage is what makes it practical for executives and program leaders.

How do we shorten the chaos phase?
Run focused pilots; provide intensive, time‑boxed support (floor walkers, huddles, fast SLAs); simplify priorities; decommission legacy tools; and aggressively capture and spread transforming ideas (checklists, templates, UX fixes). Protect capacity so people can practice.

Can we avoid the dip entirely?
Usually not for meaningful change. You can reduce depth and duration with good design, early involvement, staged rollouts, and strong enablement. Overpromising “no dip” undermines credibility.

How do we know we’ve reached the new status quo?
Adoption and proficiency stabilize at target levels, performance metrics exceed baseline and hold, new behaviors are default without extra push, and old tools are decommissioned. New hires learn the new way first.

How does Satir differ from Bridges’ Transition Model?
Satir emphasizes performance dynamics and the role of transforming ideas and practice; Bridges emphasizes the psychological phases of letting go, navigating the neutral zone, and embracing the new beginning. They are complementary lenses on the same journey.

Where should the corporate center lean in?
Set expectations for the curve with boards, provide surge support during chaos, create mechanisms to harvest and spread transforming ideas across business units, and align KPIs/incentives to reinforce the new status quo.