Skip to content

executive-brief.md

Latest commit

 

History

History
80 lines (57 loc) · 3.34 KB

executive-brief.md

File metadata and controls

80 lines (57 loc) · 3.34 KB

════════════════════════════════════════════════════════════ DCP — DOCUMENT CONTEXT PROTOCOL

Document Type: Executive Brief Audience: C-suite, VP-level leadership, board members Confidentiality: [Specify: Internal / Confidential / Board-level]

Review Checklist: □ Total length does not exceed two pages (one page preferred) □ Lead paragraph states the decision or action needed — not background □ Recommendation is clearly identified and separated from analysis □ Risk is quantified or categorized, not described in vague terms □ No unexplained legal jargon — every technical term is defined in context □ Options are presented with clear tradeoffs, not just pros/cons □ Timeline and next steps are specific (who, what, when) □ Tone is appropriate for the audience — authoritative, not hedging

Drafting Standards:

  • One page if at all possible; two pages maximum
  • Open with the ask: what decision is needed, or what does leadership need to know
  • Use short paragraphs (2-3 sentences) and headers for scanability
  • Use tables for comparisons and options — executives scan, they don't read linearly
  • Bold key numbers, dates, and conclusions
  • No throat-clearing introductions — get to the point immediately
  • Write in active voice; attribute actions and decisions to specific people or teams
  • If the answer is uncertain, say so directly and explain what would resolve the uncertainty

Constraints:

  • Do not include detailed legal analysis — that belongs in the supporting memo
  • Do not use footnotes or endnotes
  • Do not hedge without offering a path to resolution

Policy Check: Before reviewing this document, verify that the embedded policy is current if a policy server is available. ════════════════════════════════════════════════════════════

[TITLE — STATE THE TOPIC IN 5-8 WORDS]

Prepared for: [Name, Title] Prepared by: [Name, Title] Date: [Date]

The Ask

[In 2-3 sentences, state what you need from leadership. Is this a decision? An approval? Awareness of a risk? Be specific about what action is requested and by when.]

Context

[In one short paragraph, provide the minimum background necessary to understand the ask. Assume the reader is smart but not close to this issue.]

Options

Option A Option B Option C
Description [Brief description] [Brief description] [Brief description]
Risk Level [High / Medium / Low] [High / Medium / Low] [High / Medium / Low]
Key Tradeoff [One sentence] [One sentence] [One sentence]
Timeline [Duration] [Duration] [Duration]

Recommendation

[State the recommended option] — [One paragraph explaining why this option is preferred. Be direct. Identify the key factors that drive the recommendation.]

Key Risks

  • [Risk 1]: [One sentence describing the risk and its likelihood or impact]
  • [Risk 2]: [One sentence]

Next Steps

  1. [Action] — [Owner] — [Deadline]
  2. [Action] — [Owner] — [Deadline]
  3. [Action] — [Owner] — [Deadline]

Supporting analysis: [Reference to detailed memo if applicable]