How to Plan a Reorganization

A reorganization is one of the highest-stakes things a leadership team can do. Done well, it unlocks speed, clarity, and savings. Done badly, it burns trust, loses good people, and quietly costs more than it saves. The difference is almost always in the planning. Here’s a process that works.

1. Define the problem before the org chart

The most common reorg mistake is starting with boxes and lines. Start instead with the problem you’re solving. Are decisions too slow? Is the cost structure out of line with revenue? Are two teams duplicating work after an acquisition? Write the problem down in one or two sentences. Every structural decision later should trace back to it.

2. Map the current state honestly

You can’t redesign what you can’t see. Pull a complete, current picture of the organization: every role, who reports to whom, levels, and ideally fully-loaded cost per role. This is also where you’ll spot the structural issues — thin spans, deep layers, oversized support functions — that the reorg should address. (See what span of control is and what delayering is for the two patterns to look for.)

3. Design the future state as options, not an answer

Resist the urge to converge on a single design too early. The strongest reorgs come from modeling two or three future-state options and comparing them:

• A conservative version that fixes the worst problems.
• A more ambitious version that resets the structure.
• Sometimes a “do the minimum” baseline for comparison.

For each, you want to see the same facts: headcount, fully-loaded cost, spans, and which specific roles change. This is exactly what scenario modeling is for — building each option as a living model and comparing them side by side instead of arguing over static slides.

4. Cost every option

A reorg design isn’t real until it has a number attached. Each future-state option should carry its run-rate cost and the cost of getting there (severance, backfills, recruiting). Leadership decisions made without this number tend to unravel the first time finance runs their own math. Tie people-cost directly to the design so the savings you present are ones you can defend down to the role.

5. Pressure-test for risk

Before you commit, walk the design for failure modes: orphaned reporting lines, single points of failure, critical people whose roles change, spans that are now too wide to manage. A good model surfaces these automatically; a slide deck hides them.

6. Plan the sequence and the communication

A reorg is an event for the people in it. Decide the order of changes, who hears what and when, and who owns each conversation. The structure can be perfect and still fail if the rollout is chaotic. Keep a clean record of what’s changing and why — you’ll reference it constantly.

7. Execute from one source of truth

The fastest way to lose a reorg is to let fifteen versions of the plan circulate in email. Keep the plan, the financials, and the change detail in one place that everyone works from, and export the leadership summary straight from it rather than rekeying numbers into slides.

Where OrgDrafter fits

OrgDrafter is built for exactly this process: model the current org, branch future-state scenarios, cost every change automatically, and hand leadership a board-ready deck from the same model. If you’re navigating a larger transformation, carve-out, or turnaround, our transformation & restructuring solution is purpose-built for it.

Plan the problem first, model the options, cost everything, and execute from a single source of truth. That’s the whole game.