Writing executive readouts: lead with the answer, not the journey
You're trained to show your work, building up to a conclusion. Executives need the opposite: the conclusion first, the work available if anyone asks.
An executive readout is a short write-up summarizing a finding or recommendation for decision-makers. It has a different shape than how you'd naturally do the analysis. You build up to a conclusion while researching, then flip the order entirely when writing it up.
🎯 Explain Like I'm Hired A school essay builds up to its point at the end. An executive readout does the opposite: the conclusion goes in the very first sentence, because the reader might only get through that one sentence before their next meeting, and everything after it is there for whoever wants to dig deeper. Example: "We should delay the launch by 2 weeks: last week's checkout regression hasn't recovered, and shipping now risks a 5% revenue hit" leads with the decision and the why right away. The methodology (how it was measured, the test setup) belongs further down, for whoever asks.
The shape: headline, then reasons, then detail
- Headline: the recommendation or key finding, one sentence.
- Supporting points: 2-4 bullets giving the "because" behind the headline.
- Detail: charts, caveats, how it was done, for anyone who wants to verify or dig deeper.
This deliberately reverses the order you actually did the work in. Research builds toward a conclusion, but communication should start with it.
Answer the obvious follow-up before it's asked
Every finding should be paired with why it matters, and should try to head off the first question a skeptical reader would ask. If you already know someone will ask "did this account for the holiday," answer it in the readout, don't wait to be asked.
Caveats belong up front, not buried
Hiding a real limitation ("this excludes 20% of traffic due to a tracking issue") in a footnote undermines trust the moment someone finds it later. State it plainly, near the headline, not as fine print at the bottom.