Bridges Transition Model

1. What Is Bridges Transition Model?

The Bridges Transition Model is a change‑management framework that focuses on the human, psychological journey people take when confronted with change. It distinguishes between the external “change” (a new system, structure, policy) and the internal “transition” (the emotional and cognitive process people go through to let go of the old, navigate ambiguity, and embrace the new). The model maps this journey across three phases: Ending, Losing, Letting Go; the Neutral Zone; and the New Beginning.

Within the Organization function, it sits squarely in Change Management & Transformation frameworks. Consultants and executives use it to complement program plans with people‑centered actions that reduce resistance, sustain performance through uncertainty, and accelerate adoption of new ways of working.

In plain language: changes are events; transitions are how people experience them. If you manage the transition well—help people let go, guide them through the messy middle, and ignite ownership of the new—you increase the odds that the change sticks.

2. Origin and Background

The model was developed by William Bridges, a consultant and author, first articulated in “Transitions: Making Sense of Life’s Changes” (1980) and applied to organizations in “Managing Transitions” (1991; multiple later editions). Bridges drew on psychology and organizational behavior to explain why well‑planned changes often falter: leaders manage the rollout, but not the human passage from old to new identities and ways of working.

Why it was created: to give leaders a practical lens for the human side of change—separate from task plans and Gantt charts—so they could anticipate emotional arcs, communicate more effectively, and put scaffolding in place for people as they move through uncertainty.

How it spread: through management education, leadership development, and change‑management practice. It remains a common complement to program frameworks like Kotter’s 8 Steps and Prosci ADKAR.

3. How the Bridges Transition Model Works

Bridges emphasizes that transition is not the same as change, and that transition proceeds through three non‑linear but recognizable phases. Different people and groups move through them at different paces.

The three phases

• 1) Ending, Losing, Letting Go
  • What it is: The initial phase where people recognize what they are giving up—old processes, roles, status, routines, relationships, or identity markers.
  • Typical emotions: Anxiety, denial, anger, sadness, uncertainty, sometimes relief.
  • Leadership task: Acknowledge losses explicitly, mark endings, and clarify what is ending versus what will remain.
• 2) The Neutral Zone
  • What it is: The in‑between state where the old way is gone but the new way is not yet fully formed. Performance can dip; ambiguity is high; creativity and learning potential are also high.
  • Typical emotions: Confusion, impatience, experimentation, fatigue; also curiosity and innovation in pockets.
  • Leadership task: Provide direction and short‑cycle goals without false certainty; increase communication; create safe spaces to test, learn, and adjust.
• 3) The New Beginning
  • What it is: The phase where people commit to the new identity, understand the “why,” and start to internalize new behaviors; energy and performance rebound.
  • Typical emotions: Engagement, relief, confidence, ownership.
  • Leadership task: Paint a vivid picture of the future, align systems (KPIs, incentives), celebrate wins, and embed the new habits.

Core logic and implications

• Change triggers transition, not vice versa: You cannot skip the ending; people must let go of something to start something new.
• Transitions are personal and staggered: Different roles (e.g., frontline vs. middle managers) will occupy phases at different times; tailored support is required.
• Performance troughs are normal: Anticipate a dip in the Neutral Zone; design mitigating supports rather than denying its existence.
• Symbols and rituals matter: Formal markers of endings and beginnings (retire old systems, launch new ceremonies) accelerate progress.

4. When to Use the Bridges Transition Model

Most helpful when:

• You’re leading people‑intensive change—operating model shifts, restructurings, culture programs, leadership transitions, mergers, or role redesigns.
• There is meaningful loss for some groups (status, autonomy, practices), or ambiguity will persist for months (e.g., multi‑wave rollouts).
• Prior changes “stuck on paper” because human factors (resistance, fatigue, identity loss) were underestimated.

Especially powerful for: Organizational changes that alter identity (e.g., moving from product to platform business, centralizing formerly local decisions), where grief for the old way is real and must be worked through.

Use with caution when:

• The change is purely technical and low impact on behavior (minor system version updates); heavy transition work may be unnecessary.
• Leaders are tempted to use the model to rationalize slow decision‑making; the Neutral Zone is not an excuse for lack of clarity on non‑negotiables.
• You face a rapid, iterative environment; the phases still apply, but you must compress cycles and layer micro‑transitions.

Current practice: Practitioners layer Bridges with program frameworks (Kotter), individual adoption tools (ADKAR), and agile delivery. They explicitly plan for emotional and identity shifts alongside process and technology tasks.

5. How to Apply the Bridges Transition Model: Step‑by‑Step

1. Clarify the change and the likely “losses”

   Define what is changing and, crucially, what people will perceive as lost (roles, routines, influence, community, identity). For each stakeholder group, list tangible and symbolic losses. This becomes the basis for Ending‑phase actions.

2. Segment stakeholders by transition risk

   Identify groups likely to be most affected (e.g., managers whose decision rights shift, experts whose tools are retired). Rate each on exposure (extent of loss), influence, and current sentiment. Prioritize support to high‑exposure/high‑influence groups.

3. Design “Ending” actions
   • Mark the ending: Hold events/communications that acknowledge contributions of the old way; retire legacy artifacts (old templates, team names), not just systems.
   • Clarify what ends vs. what remains: Publish a simple “stop/continue/start” list by role; ambiguity fuels resistance.
   • Address fairness and support: Where losses are material (role changes), outline support paths (reskilling, redeployment, fair transitions).
   • Equip managers: Provide talking points and Q&As to discuss endings with teams; managers are the primary translators of meaning.
4. Structure the Neutral Zone
   • Set short‑cycle goals: Create 30‑, 60‑, 90‑day objectives to maintain momentum; avoid long periods of vagueness.
   • Increase communication cadence: Weekly updates, office hours, and feedback loops; normalize uncertainty and invite questions.
   • Provide scaffolding: Coaching, peer communities, pilot environments, and “floor walkers” during early adoption.
   • Protect performance: Temporarily adjust targets, headcount, or workload to offset expected productivity dips.
   • Encourage experimentation: Use safe‑to‑try pilots and retrospectives; codify and scale what works.
5. Launch and reinforce the New Beginning
   • Articulate the new identity: Describe what “good looks like” in concrete terms—behaviors, decisions, and customer outcomes.
   • Align systems: Update KPIs, incentives, governance, and role descriptions to reward the new behaviors.
   • Celebrate early adopters: Publicly recognize teams and individuals who exemplify the new way; amplify their stories.
   • Lock in the new default: Remove access to deprecated tools; embed new methods in SOPs and onboarding; update branding if relevant.
6. Measure transition progress and adapt

   Use pulse surveys and manager assessments to gauge where groups are within the three phases; track sentiment, adoption, and performance metrics. If a group remains stuck in Ending (persistent anger/denial), increase acknowledgment and clarity; if drifting in Neutral Zone, provide sharper goals; if in New Beginning, shift to reinforcement and continuous improvement.

7. Integrate with program management

   Map Bridges activities into the master plan alongside technical tasks (training, cutover). Assign clear owners for Ending, Neutral Zone, and New Beginning workstreams; ensure the steering committee reviews human‑transition metrics, not just delivery milestones.

6. Example: Bridges Transition Model in Action

Context: A $3.5B regional bank consolidated four semi‑autonomous business lines into a single segment‑led operating model (Retail, SME, Corporate). The change centralized product and risk functions and shifted decision rights from local general managers to segment heads. Prior reorganizations had stumbled due to cultural resistance and prolonged ambiguity.

Application:

• Ending, Losing, Letting Go: Leadership held town halls acknowledging the legacy of local autonomy and success stories from each region. They published a “what ends/what remains” sheet by role (e.g., pricing exceptions now under segment policy; local community programs continue). A legacy recognition program honored contributions and codified best practices into the new model.
• Neutral Zone: For 90 days, the bank ran parallel governance with weekly “decision clinics” where managers brought real cases to learn new decision rights. Temporary KPIs focused on customer continuity (NPS, complaint resolution) and process stability (turnaround times), with adjusted sales targets. A Slack channel handled gray‑area escalations within 48 hours.
• New Beginning: The CEO launched the segment model with a clear identity: “One Bank, Three Customer Engines.” New scorecards tied incentives to segment outcomes and cross‑sell. Early adopters (two regions) were recognized for faster SME loan approvals under the new shared underwriting platform; their playbooks were rolled out system‑wide. Old approval templates were retired; new SOPs and onboarding reflected the segment model.

Outcomes (9–12 months): Employee survey items tied to “I know how decisions are made” improved by 14 points. SME loan cycle time fell 18%; cross‑segment referrals rose 22%. NPS recovered to pre‑change levels by month five and exceeded it by month nine. Internal audit found 95% adherence to new decision rights. The bank avoided the prolonged stall that marred past reorganizations because leaders addressed losses, structured the Neutral Zone, and embedded the new identity.

7. Strengths and Limitations

Strengths

• Human‑centered lens: Surfaces the psychological journey often ignored by project plans.
• Anticipates performance dynamics: Normalizes and manages the Neutral Zone dip rather than being surprised by it.
• Actionable for leaders: Provides concrete tasks—mark endings, structure the in‑between, and energize beginnings—that complement technical rollouts.
• Versatile and complementary: Integrates well with Kotter, ADKAR, and agile delivery; usable across industries and change types.

Limitations

• Abstract if ungrounded: Without translation into specific actions, it risks becoming “soft” guidance leaders nod at but don’t execute.
• Not a program plan: It doesn’t replace governance, training, or benefits tracking; you must add those elements.
• Potential to excuse drift: Misused, the Neutral Zone can become cover for slow decisions; guardrails and milestones are essential.
• Measurement challenges: Gauging emotional phases relies on surveys and qualitative signals; triangulate with behavioral data.

8. Common Pitfalls (and How to Avoid Them)

• Skipping the Ending

  What goes wrong: Leaders announce “the new” without acknowledging losses; passive resistance festers.

  How to avoid: Name what’s ending; honor contributions; clarify what remains; provide fair transition support where roles change.

• Leaving the Neutral Zone unstructured

  What goes wrong: Confusion and rumor increase; performance drops further than necessary.

  How to avoid: Set short‑cycle goals, increase communication cadence, stand up coaching and rapid issue resolution, temporarily rebalance workload.

• Declaring a New Beginning prematurely

  What goes wrong: Cultural embedding lags; people revert to old habits under pressure.

  How to avoid: Align KPIs/incentives and governance before declaring victory; decommission old tools; reinforce for quarters, not weeks.

• One‑size‑fits‑all messaging

  What goes wrong: Different groups face different losses; generic comms miss the mark.

  How to avoid: Tailor messages and supports by segment (frontline, supervisors, experts); equip managers to translate locally.

• Ignoring middle managers

  What goes wrong: The “frozen middle” slows transition; frontline signals are lost.

  How to avoid: Engage managers early as sense‑makers; provide coaching, decision‑rights clarity, and recognition for modeling the new way.

• Under‑recognizing symbols

  What goes wrong: Old templates, names, or rituals keep the past alive.

  How to avoid: Retire outdated artifacts; introduce new symbols (names, rituals, visuals) that reinforce the new identity.

9. How Bridges Transition Model Relates to Other Frameworks

• Lewin Three‑Stage (Unfreeze–Change–Refreeze): Bridges deepens the “human journey” inside Lewin’s stages—Ending aligns with Unfreeze, the Neutral Zone with Change, and New Beginning with Refreeze (better, Reinforce).
• Kotter’s 8 Steps: Kotter provides a leadership sequence (urgency, coalition, vision, wins, anchoring). Bridges adds guidance on managing emotions and identity at each stage, particularly steps 1–4 (Ending) and steps 6–8 (New Beginning).
• Prosci ADKAR: ADKAR focuses on individual adoption states. Map Bridges across ADKAR: Ending supports Awareness and Desire; the Neutral Zone is where Knowledge and Ability are built amid ambiguity; New Beginning is reinforced through Reinforcement mechanisms.
• McKinsey Influence Model: Bridges complements the four building blocks (role modeling, understanding & conviction, skills, and reinforcing mechanisms) by providing a temporal lens for when to emphasize each.
• Agile/Lean Change: Agile delivery thrives in the Neutral Zone—short cycles, feedback, and iteration. Bridges encourages leaders to legitimize this phase and provide guardrails rather than prematurely forcing false certainty.
• Operating Model frameworks (7‑S, TOM): Bridges helps time the alignment of Structure, Systems, and Skills with people’s readiness across phases, reducing change shock.

10. Key Takeaways

• Bridges separates external change from internal transition and maps the human journey across Ending, Neutral Zone, and New Beginning.
• Acknowledge and mark endings; structure the in‑between with short‑cycle goals, support, and communication; then embed the new identity with aligned systems and symbols.
• Different groups progress at different speeds—tailor actions; managers are pivotal translators and coaches.
• Use Bridges alongside Kotter, ADKAR, and agile delivery to connect leadership moves, human adoption, and iterative implementation.
• Plan for the performance dip; reinforcing the New Beginning takes quarters of aligned KPIs, incentives, and stories—not a single launch event.

11. FAQs About the Bridges Transition Model

Is Bridges’ model linear?
Not strictly. People often move back and forth between phases, and different groups progress at different speeds. Treat the phases as a dominant pattern, not a rigid sequence, and tailor support accordingly.

How is Bridges different from Lewin’s model?
Lewin offers a high‑level process (Unfreeze–Change–Refreeze). Bridges focuses specifically on the psychological experience—what people feel and need in the Ending, Neutral Zone, and New Beginning—and provides leadership behaviors for each.

How do we know which phase people are in?
Use a combination of pulse surveys (sentiment, clarity, confidence), manager observations (behavioral signals), and adoption data (usage, error rates). In Ending, you’ll see grief/anger and clinging to old tools; in the Neutral Zone, questions and experimentation; in New Beginning, rising confidence, initiative, and consistent new behaviors.

What if we don’t have time for a long Neutral Zone?
You can compress it by increasing clarity on non‑negotiables, providing short‑cycle goals, ramping up coaching, and removing friction quickly. But skipping it entirely is risky—people need space to internalize and practice.

How do we handle real losses (status, roles)?
Acknowledge them directly; offer mitigation (reskilling, fair transitions); and ensure recognition of past contributions. Transparent support and fairness accelerate movement from Ending to New Beginning.

Can Bridges be used in agile transformations?
Yes. Treat agile adoption itself as a transition: mark endings (project mindset), structure the Neutral Zone with pilots and iteration, and embed the New Beginning by aligning governance, KPIs, and career models with product‑centric ways of working.

What should we measure beyond sentiment?
Track a small dashboard: adoption and proficiency, cycle times/quality (performance), escalation/resolution times (support effectiveness), and leading indicators of culture shift (manager coaching cadence, use of new forums/tools). Tie these to Value/benefits realization to keep momentum.