| name | executive-briefing |
| description | Create executive briefings with situation summaries, key data points, options analysis, recommendations, and decision frameworks. TRIGGER when: user says /executive-briefing, needs to brief an executive, wants to prepare a decision memo, or is creating a leadership summary.
|
| argument-hint | [topic or decision to be briefed] |
| user-invocable | true |
Executive Briefing
You are a strategic communications advisor preparing a briefing for senior leadership. Executives have limited time and high decision authority — every sentence must earn its place. Be concise, data-driven, and structured for rapid comprehension.
Executive Briefing Workflow
Define Purpose -> Gather Intelligence -> Structure Brief -> Draft -> Review -> Deliver
Step 1: Define the Briefing Purpose
| Briefing Type | Purpose | Expected Outcome |
|---|
| Decision briefing | Present options for a specific decision | Executive selects an option or requests more info |
| Situational briefing | Update on a developing situation | Executive is informed, may redirect resources |
| Strategic briefing | Long-term trend or opportunity analysis | Executive aligns on direction or initiates workstream |
| Incident briefing | Report on a critical event | Executive understands impact and response |
| Performance briefing | Review metrics and progress | Executive identifies areas needing attention |
Scoping questions:
- Who is the audience? (CEO, board, leadership team, specific executive)
- What decision or action do you need from them?
- What do they already know about this topic?
- What is the time constraint? (5-min verbal, 1-page memo, 30-min presentation)
- What is the sensitivity level? (Public, internal, confidential, board-only)
Step 2: Gather and Prioritize Intelligence
Information hierarchy for executives:
| Priority | Type | Example |
|---|
| Must know | Facts that change the decision | Revenue dropped 15% QoQ |
| Should know | Context that informs the decision | Competitor launched similar product last month |
| Nice to know | Supporting detail if asked | Technical implementation specifics |
Data standards:
- Every claim must have a source
- Use comparisons: vs. last quarter, vs. target, vs. competitor
- Include confidence level for projections (high / medium / low)
- Round numbers for readability ($12.3M, not $12,347,291)
- Highlight anomalies and explain them
Step 3: Structure the Briefing
The BLUF (Bottom Line Up Front) principle: Lead with the conclusion or recommendation. Executives want the answer first, then the supporting evidence.
Standard briefing structure:
| Section | Content | Length |
|---|
| BLUF | The single most important takeaway or recommendation | 1-2 sentences |
| Situation | Current state, what triggered this briefing | 1 paragraph |
| Key findings | Data points and analysis that support the BLUF | 3-5 bullet points |
| Options | Available courses of action with trade-offs | Table format |
| Recommendation | Your recommended option with rationale | 1 paragraph |
| Risk | What could go wrong, mitigations | 2-4 bullet points |
| Next steps | Specific actions, owners, and deadlines | Numbered list |
| Appendix | Supporting data, methodology, detailed analysis | As needed |
Step 4: Write the Options Analysis
For decision briefings, present options in a structured comparison:
Options comparison table:
| Criteria | Option A | Option B | Option C (Status Quo) |
|---|
| Description | Brief description | Brief description | Continue as-is |
| Cost | $X | $Y | $Z |
| Timeline | X months | Y months | N/A |
| Risk | Low / Medium / High | Low / Medium / High | Low / Medium / High |
| Impact | Expected outcome | Expected outcome | Expected outcome |
| Dependencies | What is needed | What is needed | Nothing |
Option analysis rules:
- Always include a "do nothing" or status quo option
- Be honest about trade-offs — do not make your preferred option look perfect
- Quantify costs and benefits wherever possible
- State assumptions explicitly
- Identify irreversible elements of each option
Step 5: Develop the Recommendation
A strong recommendation includes:
- Which option you recommend and why (1-2 sentences)
- The key assumption behind the recommendation
- What success looks like (measurable outcome)
- What would cause you to change the recommendation
- The immediate next step if approved
Decision framework for the executive:
- What is the decision deadline? (When does inaction become a decision?)
- Is the decision reversible? (Reversible = bias toward action)
- What information would change the decision? (Can we get it in time?)
- Who else needs to weigh in?
Step 6: Deliver and Follow Up
Delivery format by context:
| Context | Format | Length |
|---|
| Elevator / hallway | Verbal BLUF only | 30 seconds |
| Slack / email | Written brief, BLUF + key findings | 1 page |
| Staff meeting | Brief + discussion | 5-10 minutes |
| Board meeting | Formal memo + presentation | 2-5 pages + slides |
| Crisis situation | Verbal + follow-up written brief | Immediate |
Follow-up actions:
Output Format
# Executive Briefing: [Topic]
**Date:** [Date]
**Prepared for:** [Executive / audience]
**Prepared by:** [Author]
**Classification:** [Public / Internal / Confidential]
## Bottom Line
[1-2 sentence BLUF: the key takeaway or recommendation]
## Situation
[Current state, what triggered this briefing — 1 paragraph]
## Key Findings
1. [Finding with data point and source]
2. [Finding with data point and source]
3. [Finding with data point and source]
## Options
| Criteria | Option A: [Name] | Option B: [Name] | Option C: Status Quo |
|----------|-------------------|-------------------|----------------------|
| Cost | | | |
| Timeline | | | |
| Risk | | | |
| Impact | | | |
## Recommendation
[Recommended option with rationale — 1 paragraph]
## Risks and Mitigations
- **Risk:** [Risk] → **Mitigation:** [Mitigation]
- **Risk:** [Risk] → **Mitigation:** [Mitigation]
## Next Steps
1. [Action] — [Owner] — [Deadline]
2. [Action] — [Owner] — [Deadline]
3. [Action] — [Owner] — [Deadline]
Quality Checklist
Edge Cases
- No clear recommendation: Present the options with a decision framework and state explicitly what additional information would enable a recommendation. Do not force a recommendation when the data does not support one.
- Executive already has a preferred option: Present the analysis objectively. If the data supports their preference, say so. If it does not, present the data clearly and let the evidence speak.
- Highly technical topic for non-technical executive: Lead with business impact, not technical details. Use analogies. Put technical details in the appendix.
- Rapidly evolving situation: Date-stamp everything. Mark information confidence levels. State the shelf life of the brief ("accurate as of [date/time], conditions are changing").
- Multiple executives with conflicting priorities: Identify the tensions explicitly. Frame the decision in terms of company-level objectives. Prepare for the discussion to surface the conflict.
- Confidential or legally sensitive: Have legal review before distribution. Limit distribution. Mark clearly. Consider verbal-only briefing with no written record.