The Bridges Transition Model for Tech Reorgs

Change is what happens to the org chart on a Monday. Transition is what happens to people over the following three months. The two run on different calendars, and almost every reorg is planned against the wrong one.

Aldermoor Health reorganised three engineering teams into two. The mechanics were handled well: new structure announced with a month's notice, every reporting line clear, nobody made redundant, the rationale explained honestly and believed.

On the Monday it completed, and by every measure available it had gone fine.

Six weeks later, delivery was down about a third. No incidents, no resignations, no conflict. Standups were quieter. Decisions that used to take a day took a week. Asked what was wrong, people said "nothing really" — and meant it.

Nothing had gone wrong with the change. The change finished on the Monday. The transition was in its worst phase and had no end date, because nobody had planned one.

The org's calendar and the individual's calendar are different

This is the model's whole contribution, and it's the thing that makes the six-week dip predictable rather than alarming.

A change is an event: the systems cut over, the structure updates, the announcement goes out. It has a date, and on that date it is done.

A transition is a psychological process with three phases, and it starts before the change and ends well after it. Bridges' phases — an ending, a neutral zone, a new beginning — are not stages of the project. They're stages of a person.

	The organisation sees	The person is experiencing	What actually helps
Before the date	Planning, comms, prep	Ending — losing a team, a manager, an identity, expertise that no longer counts	Name what's genuinely being lost. Don't sell it as pure gain
The date	Done. Announce it	Nothing changes internally on a Monday	Resist declaring completion
Weeks 1–8 after	Why is everything slow?	Neutral zone — old way gone, new way not yet fluent	Reduce load. Say the dip is expected and finite
Weeks 8+	Business as usual, long since	New beginning — if it arrives	An early win that only works under the new structure

Read the second column against the first. On the date the organisation thinks is the finish, the individual hasn't started the hard part. The dip isn't a sign the reorg failed. It's the neutral zone, and it's the normal shape.

The test you can run: ask when your last reorg finished. If the answer is a date, you have the org's calendar. Then ask when people stopped asking who to go to for a decision — that's the transition's calendar, and it's the one that predicted your delivery numbers.

The ending is the phase that gets skipped, because it sounds negative

Leaders announcing a reorg lead with the upside — clearer ownership, less handoff, better career paths. Usually all true.

The problem is that the person listening is losing something concrete, and saying only the positive tells them their loss isn't recognised. What gets lost in a tech reorg is rarely status. It's more specific:

• The manager who knew their situation and now doesn't.

• A team they'd spent two years building trust in.

• Hard-won expertise in a system that isn't theirs any more.

• Being the person others asked — the quiet authority that doesn't survive a reshuffle.

Naming these out loud costs nothing and changes how the rest is heard. Aldermoor's second attempt at this — during a later change — included one paragraph saying, in effect: you have spent two years learning this codebase and becoming the person people ask about it, and next month that stops being true; that's a real loss and we're not pretending otherwise. The reaction was not sadness. It was relief that somebody had said it.

The failure mode to avoid is the opposite overcorrection: dwelling, apologising, or inviting an extended grievance process. Name it once, accurately, and move on.

The test: in your last change announcement, count sentences describing what people lose. If it's zero, the announcement told the affected group their experience wasn't part of the plan.

The neutral zone is where the work is, and it's the phase with no vocabulary

Weeks one to eight are where productivity drops, and they're the phase organisations have no language for — which is why the dip is read as failure, or as individual underperformance, or as evidence the reorg was wrong.

What is actually happening is mundane: people don't yet know who decides, who to ask, or which conventions survived. Every small decision that used to be automatic now costs a Slack message and a wait.

Three things help, and only one of them is communication.

• Reduce committed load, deliberately and visibly. Aldermoor now plans the first six weeks after a structural change at roughly 70% of normal commitment. Not as an admission of weakness — as a schedule that matches reality. Teams that don't do this hit their dip and miss commitments, which turns a normal phase into a performance conversation.

• Answer the routing questions faster than feels necessary. Who approves this? Who owns that service now? Publish it, keep it somewhere findable, and expect to answer the same question repeatedly for a month.

• Say the dip is expected and finite. "The next six weeks will feel slower; that's normal and it ends" is worth more than three all-hands about the vision. Without it, individuals conclude privately that they personally are struggling.

The thing that does not help is pressure. The neutral zone is not a motivation problem, and treating it as one extends it.

The test: after your next structural change, track how long the average decision takes for six weeks. If nobody is measuring it, the dip will be attributed to whoever is least able to argue.

New beginnings need something that only works in the new shape

The third phase isn't automatic. Teams can stay in the neutral zone indefinitely, running the new structure while behaving like the old one — two teams on paper, three teams in practice, with the old lines still doing the real routing.

What ends the neutral zone is a first success that could not have happened before the change — small, quick, and unmistakably attributable to the new arrangement. If the reorg was meant to remove a handoff, ship something that used to need the handoff and say so plainly.

Aldermoor's was a cross-site scheduling report that previously required two teams and three weeks. Under the new structure one team shipped it in four days. That single delivery did more to complete the transition than the announcement, the FAQ and the two all-hands combined, because it converted a claim into evidence.

The test: name the first thing your team shipped that would have been harder under the old structure. If you can't, the transition hasn't completed regardless of how long ago the change did.

Where Bridges is the wrong instrument

It describes individual psychological adjustment over time. That's a real thing and a narrow one.

• It won't tell you whether to reorganise. No view on whether the change is right, only on how it will feel.

• It has no sequencing. For the order of an organisation-wide programme, that's Kotter.

• It won't tell you why one person hasn't adopted. That's a five-gap diagnostic — ADKAR.

• It has no mechanism for making anything stick. Guardrails and defaults are Lewin's refreeze.

• The phases aren't tidy. People move at different rates and go backwards. Treating them as a schedule to be enforced misreads the model.

Its unique contribution is the time axis. It's the only one of the four that tells you when to expect the dip, and that alone changes how a reorg is planned.

The test: if your problem is "the change went fine but the team feels wrong", this is the model. If your problem is "nobody's using it", it's the wrong one.

What to do this week

If you have a structural change coming, do two things before the date.

Write one honest paragraph about what people are losing, and include it in the announcement. Not framed as regret — framed as recognition.

Then plan the six weeks after at seventy per cent, and tell people why. Naming the dip in advance is what stops it being read as failure when it arrives, by leadership and by the people living in it.

Aldermoor's delivery came back at about week nine, without intervention. What the second reorg changed wasn't the depth of the dip — it was that nobody spent it wondering whether something had gone badly wrong.