Executives have a fundamentally different set of needs during an incident than engineers do. They don't need to know which Kubernetes node is failing — they need to know the business impact, the risk exposure, and whether they need to take any action. Giving an executive a technical rundown is like reading a car repair manual to someone who just wants to know if they'll make it to their meeting.
The Liaison role (from the Incident Command structure) is responsible for this upward communication. This separation is critical: it prevents executives from calling the Incident Commander directly, which would pull the IC away from managing the technical response at exactly the wrong moment.
The BLUF Method (Bottom Line Up Front)
Military and intelligence communities developed the BLUF format for exactly this situation: communicating critical information to decision-makers who are time-constrained and context-switching constantly. The rule is simple — lead with the conclusion, then provide supporting detail.
Never bury the lead. Don't write three paragraphs of technical context before getting to "the site is down." Start with the most important sentence, then fill in the details for those who need them.
A structured executive briefing looks like this:
Subject: [SEV1] Payment Processing Down — Active Incident
BLUF: Payment processing is currently unavailable for all users globally.
Revenue impact is estimated at $X per hour. ETR: ~45 minutes.
IMPACT
- All users are unable to complete purchases.
- Support ticket volume has increased 400% in the last 30 minutes.
- Estimated revenue at risk: $X/hour based on average transaction volume.
- No data loss or security exposure identified at this time.
CURRENT ACTIONS
- Engineering team has identified the root cause (bad deployment).
- Rollback is in progress. Expected completion: 14:45 UTC.
HELP NEEDED
- Legal review requested for a proactive customer email (draft attached).
- No other leadership action required at this time.
NEXT UPDATE: 14:30 UTC or immediately upon resolution.
Incident Commander: [Name] | Incident Channel: #inc-2024-0712-payments
What Makes This Format Work
- BLUF first: The executive knows the situation in one sentence before reading anything else.
- Quantified impact: "$X per hour" is more actionable than "significant revenue impact." If you don't have exact numbers, use ranges or estimates with explicit uncertainty ("estimated $50K–$100K/hour based on last quarter's average").
- Clear ask: Executives often want to help but don't know how. Explicitly stating "Help Needed: None at this time" or "Help Needed: Legal review" gives them a clear role.
- Pointer to the IC: Executives who want more detail know exactly where to go without interrupting the wrong person.
Frequency Determines Severity Signal
The cadence of executive briefings itself communicates severity. For a SEV1 (catastrophic) incident, hourly briefings are appropriate. For a SEV2, one briefing at the start and one at resolution is usually sufficient. Establish this cadence in your first message so executives know when to expect the next update and don't fill the silence with phone calls.