Comms

War-game a town hall before you take the stage

War-game a town hall before employees, managers, and the rumor mill treat a soft script as the official company story.

Town halls fail when the narrative outruns the exhibits, when Q&A answers conflict with prior memos, when tough topics are deferred without a date, and when leaders rehearse tone instead of facts. A polished slide deck is not evidence that the room will leave with clarity instead of a second rumor cycle.

Freeze the message

State the purpose of the meeting, what has changed, what does not change, the decisions already made, and the open questions with owners and dates. Attach metrics behind any claim, prior all-hands notes, and the FAQ you actually intend to use. If the script mixes a reorg, a roadmap cut, and a fundraising update, split them. One move under fire at a time.

Write the decision you will make if the war game finds nothing new, and the delay criteria if a material contradiction or missing exhibit appears.

Seats that matter

  • Individual contributor. Clarity, fairness, and the line that feels evasive on first hear.
  • Manager. What they must explain the next morning without inventing answers.
  • Finance and people. Numbers, headcount, and commitments that must match private packs.
  • Remote and distributed. What fails when the message is only a recording and a chat thread.
  • Skeptic. The claim that looks strongest and is least sourced.

Same pack for every seat. Secret "we will tell managers later" notes create fake agreement and a worse hallway conversation.

Loop the review

Feed Pingpong the script, slides, and FAQ. First pass steelmans the message. Later passes attack from employee, manager, finance, and skeptic seats. Final pass turns surviving objections into clearer sourcing, tighter numbers, or a hold. Delete dual-counted wins and invented timelines.

Force a day-after narrative: what happens if chat fills with unanswered questions, if a metric conflicts with last month's update, or if managers cannot explain the same policy two ways. If those stories are stronger than your FAQ, fix the package before stage time.

Separate the town hall review from a layoff comms plan or all-hands message when those are also in flight. Run each as its own move so objections stay tied to one package. Related: war-game an all-hands message, war-game a layoff comms plan, war-game an internal memo, war-game a reorg, and the war-game decisions hub. Process: how to run a Pingpong.