BW-301d · Module 1

How Boards Read

4 min read

A board member arrives at a meeting having read — or scanned — a board package that may run sixty, eighty, or a hundred pages. They have read this kind of material many times. They know the filler sentences. They know the hedged language that management uses when they are not sure about something but do not want to say so. They skip past the context-setting paragraphs looking for the number, the recommendation, or the risk. If your writing does not serve the scan, it does not serve the board.

Board reading is not linear and it is not leisurely. It is triage. The board member is asking, with every paragraph: does this require my attention, or can I move on? A memo that requires sustained linear reading to extract its core message has failed. The well-designed board memo works as a scan first. The board member who reads the first sentence, the headers, and the final recommendation should have everything they need to vote. The supporting evidence is for the member who wants to go deeper — not for the member who simply needs to decide.

Do This

  • State the decision or recommendation in the first sentence or first paragraph
  • Use section headers that carry information — "Recommended: Approve $2.4M Capital Expenditure" not "Capital Expenditure Update"
  • Keep the supporting evidence subordinate to the recommendation — evidence supports, it does not precede
  • Write so that a scan produces the essential message without a single full paragraph being read

Avoid This

  • Open with context that the board already has — they were at the last meeting
  • Build to the recommendation at the end, after three pages of analysis
  • Use headers that could appear in any memo — "Overview," "Background," "Next Steps"
  • Mistake thoroughness for quality — a longer memo is not a more credible memo