The Bridges Transition Model for Tech Reorgs

Contributor
May 27
6 min read

William Bridges' transition model makes a useful distinction: change is the external event (the reorg announcement, the new tool, the new team structure), but transition is the internal psychological process that people go through to adjust. Change happens fast. Transition takes longer, and it's the transition that determines whether the change actually works.

For engineering reorgs in particular, the model is invaluable because the technical org change happens on day one and the people are stuck on day forty. Understanding why, and what to do about it, is the model's contribution.

The Three Stages

Bridges identifies three sequential stages of transition. They overlap, but the sequence is real.

1. Endings

Before someone can adopt the new state, they have to let go of the old one. This is the hardest and most underestimated stage.

For an engineer affected by a reorg, "endings" might mean:

Losing a team they identified with
Losing a manager who advocated for them
Losing ownership of a system they built
Losing a role they were known for
Losing a working agreement they liked

The error: leadership treats the reorg as a starting point ("here's our new structure") and ignores what people are losing. The team can't engage with the new because they haven't processed the old.

What helps in the endings phase:

Acknowledging what's being lost, explicitly
Naming the people, teams, and roles that are ending
Allowing time for goodbye — even if it's just an explicit "we want to recognize what this team accomplished"
Not glossing over loss with excessive optimism about the future

2. The Neutral Zone

After the ending, before the new state takes hold, there's a middle period of uncertainty. The old way is gone; the new way isn't real yet.

This stage is characterized by:

Productivity drops
People feel disoriented
Old habits keep showing up because the new ones aren't formed
People question whether the change was right
Rumors and anxiety spike

The duration of the neutral zone is often longer than leadership expects. For an engineering reorg with team restructuring, expect 2-6 months. For a major identity change (a strategic pivot, a major reduction in force), expect longer.

What helps in the neutral zone:

Acknowledging that things are uncomfortable and that's normal
Providing structure to compensate for the lack of stability — regular check-ins, clear short-term goals
Resisting the urge to keep changing things on top of the change; let the dust settle
Making space for honest feedback about what's not working
Celebrating small wins to demonstrate the new state is forming

The danger in the neutral zone is leadership concluding "this isn't working" and reversing course. Often, the neutral zone is the necessary discomfort before the new state takes hold. Reversing in the middle creates a worse outcome than completing the transition.

3. The New Beginning

Eventually, the new state becomes the new normal. People internalize the new structure, build the new relationships, learn the new patterns.

The new beginning is marked by:

People talk about the new state without qualifying it as "the new way"
New norms emerge that fit the new structure
The team's identity reforms around the new shape
Productivity recovers and may exceed pre-change levels

The trap: leadership declares the new beginning too early, before people have actually arrived. Declaring victory at week four when people are still in the neutral zone undermines trust. The people in the neutral zone know they're not "there" yet; pretending they are makes them feel unseen.

Applying the Model to a Tech Reorg

A worked example. Imagine a 50-engineer org restructuring from feature teams to platform/product teams.

Day -7 (announcement preparation): Leadership is in a different stage than the team — they've been thinking about the reorg for months and have completed their own transition. They need to remember the team hasn't.

Day 0 (announcement): This is just the change event. Transition hasn't started for anyone yet.

Week 1-2 (endings): Engineers process what's being lost. Old team Slack channels see a flurry of nostalgic messages. People reach out to former teammates. Productivity dips. This is the normal grief of the ending phase, not a sign of failure.

Week 3-12 (neutral zone): New teams are formed but not functional yet. Working agreements need to be rebuilt. Ownership boundaries are fuzzy. Some engineers question whether to stay. Productivity is below pre-change levels.

This is where most reorgs feel like they're going badly. Leadership panics, adds more meetings, adds more communication, adds more measurement — all of which can make the neutral zone longer rather than shorter.

Month 4+ (new beginning): The new teams have working norms. People stop talking about "the reorg" and start talking about the work. New patterns emerge that wouldn't have been possible in the old structure.

What Leaders Get Wrong

A few patterns to watch for.

Skipping the ending. "Don't dwell on the past — focus on the future." This sounds like positive leadership; it isn't. It denies the team's experience.

Rushing the neutral zone. Adding pressure to "get back to normal" before the team has formed the new normal. Productivity will return, but on its schedule, not yours.

Multiple changes stacked. A reorg, plus a new tool, plus a new performance review system. Each change has its own transition arc. Stacked changes create a chronic neutral zone.

Declaring success early. Announcing "the reorg is working great!" two weeks in. Engineers in the neutral zone don't believe it, and the gap between leadership's framing and the team's experience erodes trust.

Treating it as one-and-done. The reorg is announced, and then leadership moves on to other things. The neutral zone needs ongoing attention.

When the Transition Stalls

Sometimes a transition gets stuck. Signs:

People still refer to the old structure six months in
Old teams continue to function unofficially
Productivity has not recovered
Voluntary attrition spikes
New hires can't tell what the actual structure is

When the transition is stuck, the usual cause is that something about the change wasn't fully done. The old team kept meeting because the new team's purpose wasn't clear. The old ownership stuck around because the new ownership wasn't established. The transition can't complete because the change isn't actually complete.

The fix: revisit the change. What did we intend to be different? What's actually different? Where's the gap? Often a small structural completion (clarifying a role, formalizing a new working agreement) unblocks the rest of the transition.

Communicating Through the Phases

The communication pattern matches the phase.

Endings: Acknowledge what's changing and what's being lost. Don't oversell the future yet. Make space for people to express the loss.

Neutral zone: Be present. Communicate often, even when there's nothing new. The lack of communication during the neutral zone reads as abandonment. Address frustrations directly. Resist the urge to declare progress that isn't real yet.

New beginning: Celebrate the actual emergence of the new state. Specifically and concretely. Tell the story of how the team got from the old to the new.

The Model's Limits

Bridges' model is useful but has limits.

It applies best to changes that affect identity, relationships, or work patterns. It applies less to changes that are purely tactical (a new code review tool isn't the same as a reorg).

It assumes the change is staying. If leadership reverses the change midstream, the team is now transitioning twice, and the model's prescriptions don't quite apply.

It doesn't address the structural side of change. You need other frameworks for that.

It can be misread as "let the team grieve." That's not the prescription — the prescription is to acknowledge loss while still moving forward. Wallowing isn't transition; processing while progressing is.

A Cheat Sheet

| Phase | What's happening | What helps | |---|---|---| | Endings | People let go of the old state | Acknowledge loss; allow goodbye; don't gloss with optimism | | Neutral zone | Uncertainty, productivity dip, anxiety | Communicate often; provide short-term structure; resist new changes | | New beginning | New state internalizes | Celebrate emergence; tell the story; let the new norms stand |

Key Takeaway

Bridges' transition model distinguishes external change from internal transition: change is the announcement, transition is the human journey. Three phases: endings (letting go), neutral zone (uncertainty), new beginning (new state internalizes). For tech reorgs, the neutral zone is longer than leadership expects — 2-6 months for major restructuring. The most common errors are skipping the endings phase, rushing the neutral zone, and declaring victory before the new beginning has actually arrived. The model isn't a substitute for good structural change design; it's a complement that explains why the same structural change can succeed in one org and fail in another.

ShiftQuality