Executive Communication Guide
Understanding your audience
Executives differ from analytical audiences in four ways:
- Time constraint: A C-suite reader spends 60–90 seconds on a document before deciding to read further or stop.
- Decision orientation: They need to know what to do, not how the analysis was done.
- Risk sensitivity: They want to know what could go wrong, not just what is expected.
- Context breadth: They hold many competing priorities simultaneously; your work is one input among many.
Calibrate everything against these four factors.
The 60-second test
Before sending, read only:
- The subject line or title
- The first sentence of each paragraph
- The last paragraph
If a reader who did only this would understand the recommendation and the top risk, the document passes.
Structural rules for executive documents
Lead with the ask or the finding, never the background. If the reader needs background to understand the opening, put it in an appendix.
One recommendation per document. Multiple recommendations dilute focus and defer the decision. If you have three recommendations, write three documents.
Quantify the stakes. "This matters" is not a business case. "This represents $2.4M in at-risk revenue over the next two quarters" is.
Explicit next step. Every executive document should end with: "We recommend [action] by [date] by [owner]." No action, no decision.
Language guide
| Avoid | Use instead |
|---|---|
| "Interesting to note that…" | State the finding directly |
| "It appears that…" / "It seems…" | State what the data shows |
| "We ran a regression analysis…" | "Our analysis shows…" |
| "Statistically significant" | "A real effect, not random variation" |
| "The data suggests we should explore…" | "We recommend [specific action]" |
| "Further investigation is needed" | "The next step is [specific thing] by [owner]" |
Handling uncertainty with executives
Executives expect analysts to have a view, even under uncertainty. "We don't know" is a non-answer unless accompanied by what you would need to know.
Better approach:
- State your best estimate ("Our best estimate is X")
- State the confidence level ("We are confident / moderately confident / uncertain because…")
- State what would change the answer ("This assumes Y; if Y is wrong, the answer changes to Z")
Formatting for executive reading
- Bold the key finding in the opening paragraph
- No more than one chart in a one-page summary
- Bullet points over prose for supporting evidence — faster to scan
- Page 1 is the summary — everything else is backup
- Appendix for data: Move tables, methodology, and detailed breakdowns to an appendix. Don't bury the narrative in a table.
Common failure modes
Data dump: A page of tables with no interpretation. Forces the executive to do the analytical work you were hired to do.
Hedging everything: Qualifications on every sentence signal uncertainty and reduce credibility. Qualify the things that genuinely matter; don't hedge reflexively.
Missing the business context: An analysis that doesn't connect to the business problem being solved is a solution looking for a problem.
Passive conclusion: "We hope this analysis is useful" is not a conclusion. End with a decision, a recommendation, or a specific question for the executive.