Review the package before you present to the board

Before you present to the board, run the package until a skeptical director would run out of easy objections.

Board time is scarce. The pack fails when the narrative and the backup tabs disagree, when risk language softens a fact the audit committee already holds, when the ask is clear but the tradeoffs are not, or when the only alternative on the page is "do nothing" with no cost attached. Your job in private is to make those failures show up while you can still rewrite.

What the room will attack

Expect questions on cash timing, margin quality, legal and disclosure posture, customer concentration, and what happens if the lead scenario is wrong. A director who likes the strategy will still ask for the kill criteria. A director who doubts it will start with the strongest-looking unsupported claim. Build the review around those seats, not around polishing adjectives.

Also expect process questions that feel small and are not: who owns the first thirty days after the vote, what metric will tell you the decision was wrong, and which prior board commitment this ask collides with. If those answers live only in your head, the pack is not ready.

Pack the brief

One-sentence ask, owner, and decision date.
Primary exhibits: slides, appendix tabs, contracts, and counsel notes you are allowed to share.
Constraints the board already treats as fixed: cash, timing, covenants, disclosure rules.
The questions you expect from finance, counsel, and the most skeptical director.
Any claim you personally doubt but have not yet pressure-tested.
The status quo cost and at least one credible rival option written in the same format as the ask.

Run the private failure

Open Pingpong with the pack and a concrete instruction: attack weak claims, list missing evidence, and propose the smallest change that would survive the room. Sequential multi-model review fits because one pass can steelman the ask, the next can play finance and counsel, and a later pass can check whether mitigations close the hole. Ask for the reasoning behind each proposed change. Verify every factual claim against the source files before you update a slide.

Time-box the pass. Ninety minutes of attack plus source checking usually beats an overnight rewrite that reintroduces old errors. Leave with a one-page change log: claims removed, sources added, owners named, and kill criteria written. If the idea still stands after that private failure, it is ready enough for the board. If it does not, you saved the meeting for a package that can survive it.