Reorg Transition Playbook
The reorg was announced on a Monday and finished, on paper, by Friday. Six weeks later the teams still weren't working, and leadership started talking about undoing it.
A 50-engineer department moved from component teams to product-aligned teams. The announcement was upbeat; nobody mentioned the platform team that had just been split up. By week four the director declared success. By week six, ownership was fuzzy, two old teams were still meeting unofficially, and a senior engineer had resigned.
(Composite example, assembled from patterns common in engineering organisations that treat a reorg as a single event. The figures are illustrative.)
The design probably wasn't wrong. The mistake was assuming the change and the transition were the same thing. William Bridges' model (Managing Transitions, 1991) separates change, the external event, from transition, the internal journey people go through to accept it. The change happens on day one; the transition decides whether the reorg works. This playbook starts from the transition end: what people are losing, how long the in-between lasts, and what leaders do in each phase.
Step 1: know the three phases
Phase | What's happening | What helps |
1. Endings | People let go of the old state | Acknowledge the loss; allow a goodbye; don't gloss over it with optimism |
2. Neutral zone | Uncertainty, a productivity dip, anxiety (often months, not weeks) | Communicate often; give short-term structure; resist new changes |
3. New beginning | The new state is internalised | Celebrate the actual emergence; tell the story |
Step 2: lead the endings, and don't skip them
People may be losing a team they identified with, a manager who advocated for them, a system they built, a role they were known for, or a working agreement they liked. List what is ending for each group.
Group affected | What they are losing | How you'll acknowledge it |
______ | ______ | ______ |
______ | ______ | ______ |
______ | ______ | ______ |
☐ Name what's ending, explicitly: the people, the teams, the roles.
☐ Allow a goodbye: "we want to recognise what this team accomplished."
☐ Don't rush past the loss with excessive optimism about the future.
People can't engage with the new until they have processed the old.
Step 3: hold steady through the neutral zone
The old way is gone and the new way isn't real yet. Productivity drops, old habits resurface, and rumours and anxiety spike. In our experience, plan for two to six months for a major restructuring. That's a rule of thumb, not a Bridges figure.
☐ Acknowledge that it's uncomfortable and that this is normal.
☐ Provide structure to compensate: regular check-ins and clear short-term goals.
☐ Resist piling new changes on top. Let the dust settle.
☐ Make space for honest feedback, and celebrate small wins.
The danger is that leadership concludes "this isn't working" and reverses course mid-zone. Usually this is the necessary discomfort before the new state forms, and reversing usually costs more than finishing, unless the change itself was wrong, which is a different conversation.
Step 4: sketch the timeline (illustrative 50-engineer restructure)
Date each phase before the announcement, so nobody mistakes the neutral zone for failure.
When | Phase | What it looks like | Your date |
Day 0 | The change event | The announcement. Transition hasn't started. | ______ |
Weeks 1–2 | Endings | Nostalgia and a productivity dip. Normal grief, not failure. | ______ |
Weeks 3–12 | Neutral zone | Teams formed but not functional; fuzzy ownership; some question staying. It feels like it's going badly. | ______ |
Month 4 onwards | New beginning | Working norms settle; people stop talking about "the reorg". | ______ |
Step 5: don't declare the new beginning early
You're there when people talk about the work, not "the new way", and the new norms fit the new structure. Productivity recovers and sometimes exceeds the old level.
☐ Celebrate the emergence specifically and concretely.
☐ Tell the story of how the team got from old to new.
The trap is declaring victory at week four. People still in the neutral zone know they're not there, and the gap erodes trust.
Step 6: check for the common leadership mistakes
☐ Skipping the ending ("let's focus on the future").
☐ Rushing the neutral zone with pressure.
☐ Stacking changes: a reorg plus a new tool plus a new review system makes a chronic neutral zone.
☐ Declaring success early.
☐ Treating the reorg as one-and-done.
Step 7: diagnose a stalled transition
Signs that the transition has stalled:
☐ People still cite the old structure well past the window you planned for.
☐ Old teams still meet unofficially.
☐ Productivity hasn't recovered.
☐ Attrition spikes.
☐ New hires can't tell what the structure is.
If you tick several, the change probably wasn't fully done. Revisit it: clarify a role, formalise a working agreement, settle who owns which system, and the transition usually unblocks.
Wallowing isn't transition; processing while progressing is. Acknowledge the loss and keep moving.
How to use it
Who: the leader who owns the reorg, with the managers of every affected team. Run Steps 1, 2 and 4 before the announcement and the rest at regular check-ins afterwards.
Output: a list of what each group is losing and how you'll acknowledge it, a dated phase timeline, and a stall checklist you review on a schedule.
Done when: every affected group has had its ending acknowledged, the timeline has dates the leadership group has agreed not to panic against, and no stall signs remain at the review after your planned window.
Where this changes
A small team moving one or two people can run this in a single conversation: name what's ending, set expectations, and check in. A large or multi-site restructure needs more: a communications plan per phase, manager briefings before the announcement, and a named owner for the stall review. Where roles, contracts or redundancy are involved, follow the formal HR consultation process; this playbook covers the human transition, not the legal one.
The reasoning is in the Bridges transition model for tech reorgs. For the wider picture, read change management for engineering teams; for pushback, managing resistance to change in software teams. To build the case before the change, pair Bridges with Kotter's 8-step change model.
Final takeaway
The reorg is the change; the transition is what makes it work. Acknowledge what people lose, protect the neutral zone from panic and from new changes, and wait for the new beginning to show up in how people talk about the work before you declare it.
Sources
William Bridges, Managing Transitions: Making the Most of Change (Addison-Wesley, 1991; later editions with Susan Bridges). Model summary at William Bridges Associates, What is Transition? https://wmbridges.com/about/what-is-transition/
William Bridges, Transitions: Making Sense of Life's Changes (Addison-Wesley, 1980), the original statement of the three-phase model.
John P. Kotter, Leading Change (Harvard Business School Press, 1996). Kotter Inc., The 8 Steps for Leading Change. https://www.kotterinc.com/methodology/8-steps/
