executive-briefing

name	executive-briefing
type	workflow
family	workflow
rigor	full
description	Use when communicating with board members, C-suite executives, or senior leadership.
keywords	board-communication, leadership, executive, briefing, communication, C-suite
compatibility	Claude Code and compatible agent products
requires	["one-pager"]
enhances	["stakeholder-review","resonance-engine"]
sources_pdf	["The Effective Executive (Drucker)","High Output Management (Grove)","The Pyramid Principle (Minto)"]
sources_web	["HBR: Executive Communication Principles","HBR: Briefing the Board"]

Overview

Executive-briefing is the high-stakes discipline of managing senior leadership's most limited resource: attention. It shifts the focus from "reporting activity" to "delivering judgment," ensuring that every communication connect directly to organizational strategy and results in a clear decision or action.

Iron Law

NO EXECUTIVE COMMUNICATION WITHOUT BOTTOM-LINE-UP-FRONT

Buried recommendations lead to wasted executive time, tangential discussions, and "decision fatigue." If the "ask" isn't clear in the first 10 seconds, the briefing has failed.

State Machine

digraph executive_briefing_flow {
    "Briefing Input" [shape=doublecircle];
    "Step 1: Context Mapping" [shape=box];
    "Step 2: BLUF Formulation" [shape=box];
    "Step 3: Strategic Connection" [shape=box];
    "Gate: The 'Ask' Check" [shape=diamond];
    "Briefing Delivered" [shape=doublecircle];

    "Briefing Input" -> "Step 1: Context Mapping";
    "Step 1: Context Mapping" -> "Step 2: BLUF Formulation";
    "Step 2: BLUF Formulation" -> "Step 3: Strategic Connection";
    "Step 3: Strategic Connection" -> "Gate: The 'Ask' Check";
    "Gate: The 'Ask' Check" -> "Step 2: BLUF Formulation" [label="ask hidden"];
    "Gate: The 'Ask' Check" -> "Briefing Delivered" [label="ask clear"];
}

When to Use This Skill

• During Board of Directors meetings or C-suite reviews.
• When sending a "State of the Project" email to senior leadership.
• When requesting emergency resources or strategic pivots.
• During any 10-20 minute "window" with a busy executive.

When NOT to Use This Skill

• For line-level technical troubleshooting.
• For peer-to-peer collaboration where detailed background is necessary.
• During brainstorming sessions (use problem-framing instead).

Core Process

Step 1: Map Audience Context & Priorities

• Enterprise View: Identify how this topic affects the wider organization, not just your team. Executives care about Strategy, Risk, and ROI. (Source: HBR)
• Acknowledge the Pre-read: Build upon, don't restate, the materials provided earlier. (Source: HBR; Grove)

Step 2: Formulate the BLUF

• The 10-Second Rule: Deliver the core message, recommendation, or "ask" in the very first sentence. (Source: Minto; Drucker)
• Avoid "The Detective Story": Do not start with the evidence and end with the conclusion. Start with the conclusion and use the evidence to defend it only if questioned. (Source: Minto)

Step 3: Connect to Strategic Instincts