Write what leaders actually read.
Not what AI generates.

A leadership brief is a document designed to inform a decision or update a decision-maker. That's its entire job. Not to demonstrate effort. Not to cover every detail. Not to prove you did the work. To land a point, clearly, in the time the reader has.

Most briefs fail one of two tests: the reader can't find the point, or they can find it but they don't trust it. Either one puts the brief in a pile that doesn't get read.

The three modes of leadership communication

Almost every brief you write falls into one of three categories. Getting the mode right is half the battle:

• Decision briefs — you need the reader to make a choice. The brief must surface the choice, the options, and your recommendation.
• Status updates — you're reporting on progress. The brief must show what moved, what didn't, and what's coming next.
• Escalations — something is wrong or about to be. The brief must name the issue, quantify the impact, and propose action.

A brief that tries to do all three does none well. Pick the mode before you write a word.

The most important writing discipline in leadership communication is BLUF — Bottom Line Up Front. Put the conclusion first. Let the reader decide how far to read.

This is the opposite of how most people are taught to write. In school you build to a conclusion. In operations, you lead with it. Your brief is not a mystery novel; the reader should never have to hunt for the answer.

A brief to your direct manager is a different document than a brief to a board of directors, even if it's about the same topic. The audience determines the format, the tone, and what you include.

This table is your audience check. Before you write a brief, decide which row you're writing for. Everything else flows from that choice.

Claude is exceptional at turning a pile of raw information into a structured brief. The bottleneck isn't the writing — it's your ability to give Claude the right inputs. Here's the workflow.

• 1

  Pick the mode and the audience

  Decision, status, or escalation — from Section 1. Direct manager, executive, or board — from Section 3. Write both down before you open Claude.

• 2

  Gather your raw inputs

  Data, reports, meeting notes, emails, prior decisions, relevant numbers. Dump them into a document. Don't clean them up — raw is fine.

• 3

  Draft your own BLUF in one sentence

  Before Claude writes anything, you write the bottom line. If you can't say it in one sentence, you don't know what you're trying to say yet. This one sentence anchors the entire brief.

• 4

  Prompt Claude with structure and constraint

  Mode, audience, BLUF, raw inputs, target length. Claude produces the structured draft. See the template below.

• 5

  Review, revise, compress

  First drafts are always too long. Cut 20%. Tighten the subject line. Make the BLUF sharper. Compress the context. The final pass is yours — always.

The brief-drafting prompt template

ROLE: You are a senior operations communications specialist. You write clear, direct leadership briefs to a professional standard. BLUF discipline is non-negotiable.

CONTEXT: [Who I am, what operation, my relationship to the decision or situation.]

AUDIENCE: [Specific reader. Seniority. Relationship. What they already know.]

MODE: [Decision brief / Status update / Escalation.]

MY BLUF: [Your one-sentence bottom line. Claude opens the brief with this — refined but not reinvented.]

RAW INPUTS: [Paste everything — data, notes, emails, numbers. Unorganized is fine.]

TASK: Draft a leadership brief using this structure: Subject line, BLUF, Context, Key Facts (3–5 bullets), Options/Analysis, Recommendation/Ask, Appendix (if needed). Match length to audience: one page for direct/executive, two to three for board.

STANDARD: Lead with the point. No throat-clearing. No adjectives where a number works. Flag anywhere my raw inputs contain gaps or contradictions — do not invent facts. The brief should sound like it was written by an experienced operator, not by a generative tool.

The signature of AI writing is not bad grammar. It's a hollow, hedged, middle-management tone — the kind of writing that hedges every claim, softens every conclusion, and ends every section with a transition phrase. That tone is recognizable at 20 paces, and it undermines the credibility of everything under it.

Your job is to eliminate it. Here's what to train Claude to avoid, with examples:

The voice-calibration technique

The single best way to make Claude write in your voice: paste two or three samples of your own writing — briefs, emails, memos — into the prompt with the instruction: "Match the tone, vocabulary, and rhythm of these samples. I wrote them. The final brief should be indistinguishable from my own writing."

Claude is very good at this. Most people skip it because it takes 30 seconds of preparation. That 30 seconds is the difference between a brief you'll sign and a brief you'll rewrite.

Here's what a one-page executive decision brief looks like when this process is done well. Context: you're an operations director, recommending a capital expenditure to your CEO.

That's the whole brief. One page. Seven parts. The CEO can read the BLUF in 15 seconds and have everything they need to approve. If they want more, it's right there. This is what the workflow in Section 4 produces, once you've done it a few times.