Change adoption / personal transition
Bridges' Transition Model
William Bridges' distinction between change and transition, and it is the most useful sentence in change management: change is external and happens on a date, transition is internal and takes as long as it takes.
Every transition starts with an Ending, passes through a disorienting Neutral Zone, and only then reaches a New Beginning. Organizations announce the change and assume the transition happened at the same moment, which is why go-live day so reliably produces a workforce that has technically moved and psychologically has not.
- Problem
- Change adoption / personal transition
- Altitude
- Individual to enterprise
- Effort to run
- Light
- Evidence base
- Emerging
Theory & origin
William Bridges set out the model in Transitions (1980) and Managing Transitions (1991), and its whole force sits in one distinction. Change is situational and external: the new structure, the new system, the merged team, all of which happen on an announced date. Transition is psychological and internal: the process a person goes through to come to terms with the new situation, which starts before the change and finishes long after it. Bridges names three phases, and insists they must be gone through in order. The Ending, Losing, and Letting Go comes first, because every transition begins with something finishing, and the work here is naming what is actually being lost, competence, colleagues, status, a familiar routine, and letting people grieve it rather than being told to look forward. The Neutral Zone follows, and it is the hardest and most important phase, an in-between where the old way is gone and the new way is not yet fluent. Productivity dips, anxiety and ambiguity are high, and people feel incompetent, but it is also, Bridges argues, the most creative period available, because old habits have loosened and new ones have not set. Skipping or rushing it is the classic mistake. The New Beginning comes last, and cannot be forced by an announcement, since it starts when people find their own new identity, competence, and purpose in the new arrangement. The model's practical claim is that resistance is usually not opposition to the change but grief over the ending, and that leaders who mark the ending honestly, staff and support the neutral zone, and let the beginning arrive rather than mandating it, get through in a fraction of the time. It pairs cleanly with Kübler-Ross, which describes the emotional reaction, and Lewin, which describes the system physics, while Bridges describes the personal passage.
Key components
The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.
Explore the model
the ending: name what is lost, and let it be grieved
How a consultant runs it
- 01 Separate the change from the transition in the plan itself. The change has a go-live date, the transition does not, and a plan that treats them as the same date is planning to fail on day one.
- 02 Mark the ending out loud. Name what is genuinely being lost, competence, colleagues, routine, status, and let it be mourned, because an unmarked ending stalls the entire passage.
- 03 Staff the neutral zone rather than rushing it. Temporary structures, extra support, tolerated dips, and short feedback loops, because this is where productivity falls and where people quit.
- 04 Do not sell the new beginning during the ending. Enthusiasm aimed at people who are still losing something reads as dismissal and hardens resistance.
- 05 Watch for people in different phases at once. A leadership team that transitioned months ago during planning is a phase ahead of the staff, and mistakes that gap for resistance.
When to use
- 01 Planning the people side of any change, alongside the technical and structural plan
- 02 Explaining why a technically complete rollout still is not working weeks later
- 03 Coaching leaders who transitioned during planning and cannot see why their staff have not
When not to use
- 01 As a substitute for actually managing the change. It describes the passage, it does not run the project.
- 02 As a rigid, uniform timetable. People move at different speeds and loop back, and the phases overlap.
- 03 For small, welcome changes with nothing meaningful to lose, where inventing an ending manufactures drama.
Worked example
A multifinance lender migrates from a manual, relationship-driven credit process to an automated scoring platform, and the project plan calls it done on go-live day. Six weeks later the platform runs perfectly and the business does not. Bridges explains the gap.
The Ending was never marked: the senior analysts whose judgment had been the credit function's core asset quietly lost the thing that made them respected, and nobody named that loss, so they were left with a status bereavement no one acknowledged while being told to be excited about efficiency.
The Neutral Zone was neither planned nor staffed: for weeks people ran the old spreadsheets alongside the new tool, output fell, errors rose, and because the plan had no room for a dip, the drop was read as underperformance and managed with pressure, which made it worse.
And the New Beginning was declared by memo on day one, so the leadership team, who had transitioned months earlier during design, saw everyone still in the neutral zone and diagnosed resistance. The recovery is straightforward once the phases are separated.
The ending gets marked honestly, in a session that names what the experts lost and what their judgment will still be for, namely the complex cases the model cannot score.
The neutral zone gets resourced, floor support, a tolerated productivity dip in the targets, and a weekly forum to fix the tool's real problems. And the beginning is allowed to arrive rather than announced, visible eventually when analysts start proposing their own improvements to the scoring rules.
The technology had been ready in a week, and the people needed a quarter, which the plan should have said from the start.
Common pitfalls
- 01 Treating go-live as the end of the transition, when it is only the start of it
- 02 Skipping the ending, so an unmourned loss quietly stalls the whole passage
- 03 Leaving the neutral zone unplanned and unstaffed, then punishing the predictable dip
- 04 Declaring the new beginning by announcement, which cannot create it
- 05 Leaders who transitioned during planning mistaking a phase gap for staff resistance
Sample deliverable
One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.
Input
- The change (technical go-live)100% at week 1
- Ending accepted35% at week 6
- Through the neutral zone20% at week 6
- New beginning reached5% at week 6
Process
The change finishes on go-live, and each transition phase is tracked by how far people actually are
Platform migration: change complete, transition not
- Gapthe system was done in a week, the people needed a quarter
- Fixmark the ending, staff the neutral zone, let the beginning arrive
- Signalanalysts start improving the new process, not just using it