The 12-Minute Board Briefing.

Every senior finance professional has a Sunday-night version of the same problem. Twelve scattered files. Three voice notes. A folder of half-written observations. And on Monday morning, a board with strong opinions and short attention spans.

The brief itself is not the hard part. Senior people know what a clean board memo looks like. The hard part is the twenty minutes between scattered material and a defensible first page.

This briefing walks through the exact workflow most members keep using once they see it. The whole thing runs in under fifteen minutes, including review.

The setup

You are preparing a board memo. You have your own notes from the quarter, an exec summary from finance, two emails from the chair, and the prior-period memo for context. You do not want a generated draft to sound like a machine wrote it. You want it to sound like you wrote it, just faster.

Two rules before anything starts.

• No identifying details. No client names, no private financial specifics, no MNPI. Use placeholders: [Portfolio A], [8-figure revenue], [Board Member 1].
• You write the framing, AI writes the connective tissue. Your three big points are yours. Claude tightens, sequences, and clarifies, it does not decide.

The prompt, sanitized.

You are helping me prepare a board memo. I will paste my raw notes
and three reference documents. Do this in order:

1) Identify the 3 strongest themes a board would actually care about.
2) For each theme, write one tight paragraph (under 90 words) using
   only the language used in the source.
3) End with 2 questions the board is likely to ask.
4) Flag any place where the source is thin or contradictory.

Tone: senior, plainspoken, no jargon. No filler.
No marketing language. No "in today's environment" phrases.

Replace any names with [Company A], [Member 1], [Region X].

That is the whole prompt. You paste your sanitized material below it. You do not need to be clever. You need to be specific.

What actually comes back

You get three themes, three tight paragraphs, two anticipated questions, and a short list of weak spots in the source material. The themes are usually right. The phrasing is your phrasing. The questions are useful, you will use one of them in the meeting.

This is where most professionals stop and try to publish. Do not. The output is a baseline, not a memo.

The output is a baseline, not a memo. The senior professional applies judgment before anything leaves the document.

The 15-Minute Senior Review

This is the part of the workflow that makes it defensible. The review takes about ten minutes once you have done it twice. Steps:

1. Read the three paragraphs out loud. Anything that does not sound like you, cut.
2. Add the one fact you know but Claude could not, a relationship, a known sensitivity, an off-record context.
3. Replace placeholders with the real names. Do this manually. Do not paste a key file.
4. Re-read the two anticipated questions. If they are obvious, write the answer in two sentences and add it to the memo.
5. Sign off in your own voice, the last paragraph is yours, every time.

What you have on screen is the board memo, in roughly the same time you used to spend on the email saying you were running late.

Why this works

The 12-Minute Board Briefing works for three boring reasons.

First, the prompt does not ask for a draft. It asks for a structure. Structure is what most senior professionals are short on, not words.

Second, the workflow assumes a review layer. It does not pretend the model will catch its own blind spots. The senior professional is the last word, in writing, every time.

Third, it does not save the most time on the easy weeks. It saves the most time on the hard weeks, the ones where the material is messy, the topic is contested, and there is no time to start from a blank page.

What it does not do

It does not write your strategic point of view. It does not handle confidential material. It does not replace the meeting prep itself.

It writes the page that makes the meeting prep five minutes shorter.

That is the whole point.

---

Filed under Workflows · The Leverage Years · Vol. I, Issue 14.