Lesson 1 · Writing
Writing for executives
Put the answer first. Busy readers decide in the first two lines whether to read the rest.
Engineers are trained to write the way they solve problems: context, investigation, findings, conclusion. Executives read the other way round. They have thirty documents a day and want to know, first, what you need from them. BLUF — bottom line up front — puts the conclusion or the ask in the opening sentence, then gives the reasons, then the detail for anyone who wants it.
The pyramid principle (Barbara Minto) structures the rest. Start with one governing thought. Support it with three or so key points that do not overlap and together cover the case. Support each of those with evidence. If a reader stops at any level, they still leave with the right conclusion. For a problem write-up, SCQA is a useful opening: Situation, Complication, Question, Answer.
Then cut. Replace adjectives with numbers (“p99 latency rose from 180 ms to 900 ms”, not “latency got much worse”). Say what decision you need, from whom, and by when. Put options in a table with a recommendation. A one-page memo that someone reads beats a ten-page document that someone skims — and writing it forces you to know what you think.
Picture it
An engineering manager's first draft about a database migration opens with two paragraphs on the history of the schema. Her director replies: “What do you need from me?” She rewrites the opening line: “I need approval by Friday to spend $40k on a managed Postgres migration; it removes our top cause of incidents and pays back in seven months.” Three bullets follow, then an appendix. It is approved the same day.
Key formulas & frameworks
- BLUF
- Bottom line up front: the ask or conclusion in sentence one
- Pyramid principle
- One governing thought → 3 key points → evidence
- SCQA
- Situation → Complication → Question → Answer
- The ask
- What decision · From whom · By when
Practice
Score: 0 / 5
Go deeper
- How to write for executives: BLUF and the pyramid principleArticle · 6 min read
- How to write a design doc that gets a decision madeArticle · 6 min read
- Executive communication cheat sheetPrintable cheat sheet
Up nextPresenting to leadership
Next lesson