Board meeting prep

Purpose

A board can only use a meeting for judgment if the context has already been read. This skill builds the material in the order that makes that possible: who is in the room, what decision is needed, what the board must believe to say yes, the evidence for each belief, and a discussion plan. Slides come last.

When to use

• A board, investor, or executive committee meeting is coming up and needs a decision.
• A new leader is presenting go-to-market performance for the first time.
• Directors keep asking why growth is not faster, and the answer has not been framed.

If no decision is needed, the material is a report. Send it as a memo, not a board presentation.

Route elsewhere when:

• The question is the revenue model or forecast. Use revenue-metrics or revops-forecasting.
• The question is the company's internal operating cadence. Use revenue-operating-cadence.

Inputs

• The meeting date, the attendees, and the directors' known interests.
• The decision or decisions the room must make.
• The performance data for the period, and the standing report format if one exists.
• Any capital request, with its cost, the expected return, and what has already been proven.

Procedure

1. Name the audience. For each director, write the lens they will apply (benchmarking, capital efficiency, execution, governance) and the question they are most likely to ask.
2. Write the primary decision. One decision. Add up to two secondary asks for advice or input. If there is no decision, send a memo instead.
3. State the story. Write what the board must believe to say yes, in three governing claims at most. Each is a claim, not a topic.
4. Place the evidence under each claim. One conclusion per exhibit, stated in its title. Deep detail goes to an appendix, to be shown only if a director asks.
5. Run the altitude check. Restate every finding at the level of the company. A board asks what limits growth, what sequence removes it, and where the board can help. A report on one function is a correct answer to a smaller question. Rewrite it as the company constraint, the cross-functional sequence that addresses it, and the action only the board can take.
6. Frame any capital request as a comparison. Show the chain from investment to result, what has been proven at a smaller scale, the milestone that releases the next tranche, and the cost of delay.
7. Design the room. Retrospective, then orientation, then the decision. Plan the time at about 25 percent presentation and 75 percent discussion.
8. Close on a named decision: who, what, by when, and what it unlocks. Record it in writing within one business day.
9. Send the pre-read seven calendar days ahead, and never fewer than five business days ahead. Directors read it, so the meeting itself is for judgment.

Output

• Director map with lenses and likely questions.
• The decision brief: primary decision, secondary asks, the claims, and the evidence under each.
• The pre-read, written so it can stand alone.
• The room plan with timings.
• A list of likely director questions and the answer to each.

Quality bar

One primary decision is stated in the first two minutes. Findings are at company altitude. Capital requests are compared, not stood alone. The pre-read goes out on time. The meeting ends with a recorded decision with an owner and a date. Watch for a pre-read presented aloud, forecasts defended instead of causal chains, and no decision named at the end.