War-game a reorg before you redraw the chart so reporting lines, decision rights, and customer impact fail in private first.
Reorgs often solve a slide problem and create an execution problem. People lose clear owners, customers bounce between teams, and the real bottleneck moves instead of disappearing. Announcing before you can name decision rights and success metrics is how trust drains in the first week.
Name the problem the reorg claims to fix
Write the failure mode in one sentence. Examples: decisions stall across product and GTM, support cannot find an owner, or two teams ship overlapping roadmaps. Then write the post-reorg owner for that failure mode. If you cannot name the owner, the chart is decoration.
Freeze the spans of control, the decision rights matrix, the customer contact map, and the first ninety-day outcomes. Attach the before-and-after org, the budget impact, and the transition plan for open work. Split any secondary goals into separate decisions. One reorg under fire at a time.
Hostile seats
- Staff seat: what breaks in day-to-day ownership and career paths.
- Customer seat: who they call next week and what response time gets worse.
- Finance seat: duplicate cost, contractor overlap, and the savings that only exist on paper.
- Execution seat: the first program that will stall during the transition.
- Skeptic seat: the claim that looks cleanest and has the least evidence.
Ask each seat for material objections, missing owners, and the smallest change that keeps the intent without the chaos. Optional counsel seat if the reorg touches employment terms or works councils.
Private pass
Run that package in Pingpong. Sequential review helps because an early pass can defend the redesign while later passes try to kill soft ownership claims. Keep a change log of decision rights clarified, roles renamed, and transition risks accepted. If survival requires silence about customer impact, stop. Rewrite the plan or delay the announce.
Publish the transition calendar inside the package: who owns each open program during the cutover, when titles change, and when customer routing flips. A reorg without a dated handoff is a rumor with an org chart. Ask the execution and customer seats to break that calendar before anyone sees the announce draft.
Related: before you reorg, before you announce layoffs, war-game your strategy, CEO decision review, role-play strategy review, and AI for high-stakes decisions. Mechanics: how it works.