War-game a hiring freeze exception before finance, hiring managers, and the wider team hear it as favoritism or a silent reopen of headcount.
An exception is not a small admin note. It changes the freeze story, the queue of other managers who will ask next, offer letters already paused, and the credibility of the original cash plan. Shipping an exception without a seating chart review usually means you learn the hard objections in the first week of "why them, not us" threads, not in a private pass.
Freeze the exception
State the role, the business reason, the cash and equity impact, the approval owner, and the sunset or review date. Name which other open reqs stay frozen and what customer or product commitment this hire uniquely protects. If the memo mixes an exception with a reorg and a budget cut, split them. A war game needs one move under fire at a time.
Write the decision you will make if the war game finds nothing new. Also write the reverse criteria: the attrition spike, fairness complaint, or forecast miss that would retract the exception or reopen a broader hire review.
Seats that matter
- Finance. Cash timing, runway math, and whether this exception breaks the freeze forecast.
- Peer hiring manager. Equity across teams, copycat requests, and the first ninety days of thinner coverage elsewhere.
- Candidate and market. Whether the role can still fill, and employer brand risk if the freeze story flipped.
- People and morale. Retention risk, rumor surface, and the message that makes key people feel the freeze was selective.
- Skeptic. The claim that looks strongest and is least sourced.
Attach the same source pack to every seat: freeze memo, open reqs, offers in flight, protected bets, and the exception policy you actually intend to use. Secret data for one seat creates fake agreement.
Loop the review
Feed Pingpong the exception brief, the freeze memo, and the seating briefs. First pass steelmans the exception. Later passes attack from finance, peer manager, candidate, and morale seats. Final pass turns surviving objections into a narrower scope, a time-boxed hire, or a declined exception. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
If quiet add-backs are the real risk, force the review to invent the exception policy before approve. An exception that only works with silent siblings is not an exception. It is a shadow headcount plan with worse reporting. Write the approval owner, monthly cap, and publish rule into the package, then ask finance and peer manager seats to attack those rules.
Pair with war-game a headcount freeze, war-game a hiring plan, before you hire, war-game a budget cut, war-game a comp review, and the war-game decisions hub. See how it works.