War-game a layoff communications plan before internal rumor, external screenshots, and uneven manager scripts define the story for you.
Layoff messaging fails when the "why" and the numbers disagree, when managers learn after the press, when remaining teams cannot answer customer questions, and when counsel discovers a phrase that creates legal exposure. A polished all-hands draft is not evidence that the package survives the first hour.
Freeze the comms package
Lock the populations in scope, the timing sequence (who hears first), the channels, the claims you will make about cause and future plans, and the owners for manager kits and customer notes. Attach headcount math, prior public statements, WARN or notice constraints where they apply, and the FAQ you intend managers to use. If people, legal, and finance tell different stories about the "why," stop and reconcile before any seating pass.
Write the decision you will make if the war game finds nothing new, and the hold criteria if a material risk appears in legal, sequencing, or customer impact.
Seats that matter
- Counsel. Phrases that create liability, uneven treatment claims, or premature disclosure risk.
- People and morale. What remaining teams will believe, and what makes key people leave.
- Customer and partner. Delivery risk, support coverage, and the questions renewals will ask.
- External reader. How press, social posts, and candidates will frame the note.
- Skeptic. The strongest-looking claim with the weakest source.
Give every seat the same pack. Secret "we will hire right back" lists for one chair create fake calm and angry remaining staff later.
Private failure loop
Feed Pingpong the drafts, sequence, and exhibits. First pass steelmans the plan. Later passes attack from counsel, people, customer, and external seats. Final pass turns surviving objections into tighter claims, clearer sequencing, or a hold. Delete invented future hiring promises and dual-counted savings.
Force a day-after narrative: what screenshots circulate, which customers escalate, and what managers improvise when the FAQ is thin. If those stories are stronger than your sequence, fix the package before send. Separate the decision to reduce headcount from the communications plan. This page is for the message under fire; pair it with the decision guides that cover the cut itself.
When customer-facing roles are in scope, force a support and sales FAQ into the same war game as the internal note. Ask the customer seat to invent the ten hardest renewal questions, answer them with owners and dates, and either edit the external note or consciously leave a known risk off the page. Uneven external scripts create rumor as fast as a leaked internal draft.
Nearby: before you announce layoffs, before you let someone go, war-game an all-hands message, review a crisis comms plan, war-game a headcount freeze, and the war-game decisions hub. See how to run a Pingpong.