Communication
How to write for executives: BLUF and the pyramid principle
Why engineers' emails and docs get skimmed by leadership, and how BLUF, the pyramid principle and SCQA get your request read and approved.
· 6 min read

Most engineers write the way they debug: here is the context, here is what we tried, here is what we found, and — at the bottom — here is what we should do. It is a fine order for thinking. It is the wrong order for a reader who has thirty other documents waiting and will decide in two lines whether yours deserves attention.
Bottom line up front
BLUF comes from military writing, where a reader might have to act on the first sentence alone. Put the conclusion, or the thing you need, first. Then the reasons. Then the detail, for whoever wants it.
- Before: “Over the last quarter the team has investigated several options for our CI pipeline, which has become a growing source of frustration…”
- After: “I recommend we move CI to a managed service by March. It halves build times and costs $2,000 a month; I need your approval by Friday.”
The second version can be approved from a phone between meetings. The first will be read later — which often means never.
The pyramid principle
Barbara Minto's pyramid principle is BLUF applied to a whole document. Start with one governing thought. Support it with about three key points that do not overlap and together make the case. Support each point with evidence. A reader who stops at any level still leaves with the right conclusion; one who wants to check your reasoning can keep going down.
A quick test: read only your headings in order. If they tell the story on their own, the structure works.
SCQA for problem write-ups
When you need to explain a problem before the recommendation makes sense, open with SCQA:
- Situation — what is true and uncontroversial. “Checkout handles 40,000 orders a day.”
- Complication — what changed. “Since the October release, 2% fail at payment.”
- Question — the one it raises. “How do we stop losing those orders?”
- Answer — your recommendation. “Roll back the retry change and add a canary stage.”
Then cut
- Swap adjectives for numbers. “p99 latency rose from 180 ms to 900 ms” beats “latency got much worse”.
- Make the ask explicit: what decision, from whom, by when.
- Put options in a short table with your recommendation marked.
- Move methodology, history and caveats to an appendix.
- Aim for one page. Writing it short forces you to know what you think.
None of this is about dumbing things down. It is about respecting the reader's time — and a manager whose writing is easy to act on gets more decisions made.



