Working with people
Bottom line up front
Put the decision, ask or outcome in the first sentence. Context comes after.
Busy people decide whether to keep reading in the first two lines. If those lines are background, background is what they remember. BLUF (bottom line up front) means the first sentence answers the real question: what happened, what you need, or what you recommend.
Concept
BLUF is a writing pattern from military and executive work: state the conclusion or ask first, then support it. It is the opposite of academic writing, which builds toward a thesis.
The big idea
Academic writing trains you to warm up. Engineering writing cannot afford that. Your manager, a PM, or an on-call peer is skimming a phone on the way to another meeting. Give them the point, then the path.
The analogy is a newspaper headline, not a mystery novel. A headline that waits until paragraph four is not a headline. The analogy breaks when the reader truly needs the mechanism first — a design review among people who already share the decision. Even then, one BLUF sentence still helps: "Recommend option A; the rest is why."
Walking through it
Compare the same ask.
| Style | Opening |
|---|---|
| Academic | "As we discussed last week, the checkout service has been experiencing elevated latency due to…" |
| BLUF | "Need decision by Thursday: ship the cache fix behind a flag Friday, or delay the launch one week. Details below." |
The second version lets a skimmer act. People who care about the path can scroll. Nobody has to reverse-engineer your conclusion.
Apply BLUF wherever a reader must decide or unblock you:
- Slack: first line is the ask, not "hi" and a wait.
- Email and docs: first paragraph is the recommendation.
- Meeting openers: "We're here to pick A or B; here's the trade-off in 60 seconds."
- Subject lines: treat them as the whole message for people who never open the rest.
A useful edit: delete the first paragraph. If the second already contains the point, the first was throat-clearing.
Example
You need two days for a migration. Weak: "Thoughts on cleaning up the old API?" Strong: "Approve 2 eng-days this sprint to delete the v1 checkout API (already unused in prod per logs). Risk if we wait: every new feature still touches dead code. Need yes/no by Wed."
Common mistakes
- Warming up. "As we discussed…" and "just wanted to share" burn the two lines that matter.
- Hiding the ask. A perfect analysis with no "need X by Thursday" is a status novel, not a request.
- BLUF without a default. If nobody answers, what happens? State the fallback: "If no reply by Friday noon, we delay."
Check yourself
- Rewrite this opener as BLUF: "We've been looking at checkout latency and wanted to share some findings from last week's investigation."
Lead with the outcome and the ask, then the investigation: "Checkout p99 is 800 ms; recommend shipping the cache fix behind a flag Friday. Need a go/no-go by Thursday."
- When is a long setup acceptable before the point?
When the reader already shares the decision and needs the mechanism — and even then, one BLUF sentence at the top still helps.
Key takeaways
- The first sentence should be the decision, the ask or the outcome.
- Subject lines and first Slack lines are BLUF in miniature.
- Delete the warm-up paragraph if the next one already has the point.
Further learning
Next: writing for skimmers. Google's technical writing courses drill the same habit.
Technical Writing courses (Google)Technical Writing Courses for EngineersGoogle for Developers
Related
Written and verbal communication
Lead with the point, write for skimmers, and adjust depth for engineers, PMs and executives.
Writing for skimmers
Assume a tired reader on a phone. Headings that say something, one idea per paragraph, links instead of dumps.
Status and decision updates
Shared templates for status, incidents and decision requests so readers know where to look.