Lead With the Point (BLUF)

The part overview argued that communication is the core skill of management: nothing you decide, plan, or care about matters until it lands in someone else’s head accurately. This page is the first and most practical move in making that happen. It’s small, it’s learnable, and it will improve almost everything you write and say this week.

The move is this: lead with the point. Say what you want the other person to know, feel, or do — first — and put the reasons underneath. In writing this is often called BLUF: Bottom Line Up Front. It sounds obvious. Almost nobody does it. This page explains why we bury the point, why that costs the reader, and how to stop.

The principle: the point goes first, the reasons go second

Most messages are written in the order the writer discovered them. You had a problem, you thought about it, you weighed some options, you reached a conclusion. So you write it in that sequence: here’s the background, here’s what I considered, here’s what I found, and — finally, at the bottom — here’s what I want. That’s the order of your thinking.

But the reader doesn’t need your thinking; they need your conclusion. Leading with the point flips the order:

BURIED (writer's order)          BLUF (reader's order)
─────────────────────           ─────────────────────
Background                       The point / ask       ← first
Context                          The deadline
Options considered               Who owns it
Analysis                         ─────────────────────
...                              Background
The point / ask      ← last     Context (for those who need it)

Both messages contain the same information. But in the first, the reader has to wade through everything to find out what you want — and often gives up, skims, or misreads. In the second, they get the point in one sentence and can choose how deep to go. Put the conclusion, the decision, or the ask in your first sentence. Everything else is support.

In practice — the same email, two ways

Buried: “Hi team — hope everyone’s well. I was going over the numbers from last quarter and noticed a few things about the onboarding flow, and I had a chat with support who mentioned some recurring tickets, and it got me thinking about whether we should revisit how we handle new signups before the busy season…”

BLUF: “I want us to redesign the signup flow before December. Two reasons below.” Then the reasons. A busy reader knows in five seconds what you want and when. The one who needs the why keeps reading; the one who just needed the ask is already acting.

Why we bury the point: the curse of knowledge

If leading with the point is so obviously better, why is burying it the default? The answer is a quiet trap called the curse of knowledge: once you know something, it becomes very hard to imagine not knowing it.

You have all the context in your head. You know the backstory, the constraints, why this matters, what you’re really asking for. So the context feels like the natural starting point — you don’t notice you’re making the reader climb the same hill you already climbed. To you, the conclusion feels like it needs all that setup. To them, the setup is just noise until they know what it’s for.

Here’s the cost. When the point comes last, the reader has to read the whole thing while holding an unanswered question: what does this person actually want from me? They’re reverse-engineering your intent from clues, guessing at the destination while you narrate the journey. That’s real cognitive work, and busy people don’t do it — they skim to the bottom, or they reply “not sure what you need here,” or worst of all, they assume what you want and get it wrong.

The common trap — “but they need the context first”

The most common objection to BLUF is: “If I state the ask cold, without setup, it’ll seem abrupt or they won’t understand it.” This confuses two different things. The reader doesn’t need the context to understand the ask — a good ask is self-contained. They need the context to evaluate or agree with it, and that can come after. Give the point first for comprehension; give the reasoning second for buy-in. If you’re worried it sounds abrupt, add one warm line — but keep the point in sentence one.

The evidence — attention is front-loaded

Studies of how people read on screens generally find that attention drops off sharply after the first line or two — readers scan, they don’t study. Roughly speaking, if the point isn’t near the top, a large share of readers never reach it. This isn’t laziness; it’s how attention rations itself against a flood of messages. Writing for how people actually read — point first — isn’t dumbing down. It’s respect for a finite resource.

The point is not the topic

Here is the single most useful distinction on this page, and the one people most often miss.

• The topic is what your message is about. (“The signup flow.” “The Q3 budget.” “The night-shift rota.”)
• The point is what you want to happen as a result. (“Approve the redesign by Friday.” “Cut travel spend by 10%.” “Two nurses swap shifts next Tuesday.”)

People lead with the topic and think they’ve led with the point. “I wanted to sync on the thing” names a topic — a vague one — and leaves the reader with no idea what you want. “Can we talk about the budget?” is a topic. “I need you to approve $8k for new equipment by Thursday, and I’d like ten minutes to walk you through why” is a point.

TOPIC (what it's about)          POINT (what you want to happen)
"wanted to sync on the thing" →  "I need a yes/no on the vendor by Friday"
"about the schedule"          →  "I'm asking you to cover Saturday's late shift"
"following up on the incident"→  "Please add a second check to the release
                                  step so this can't repeat"

A topic tells the reader which drawer to open. A point tells them what to do. If your first sentence names a subject but not an action, a decision, or a piece of knowledge you want them to hold — you’ve led with the topic, and you haven’t actually said anything yet.

In practice — the meeting invite

A calendar invite titled “Catch-up” is a topic; nobody knows how to prepare or whether they’re even needed. Retitle it “Decide: which vendor for the new phone system” and the point is now doing work before the meeting starts — people know it’s a decision, they know what to bring an opinion about, and the meeting is shorter because it opens already aimed.

A concrete “point-first” ask

When your message needs someone to do something, a clear ask names three things. Missing any one of them is where “clear” messages quietly fail:

1. The ask — what specifically you want done. (Not “look into this” but “approve,” “review,” “decide,” “send.”)
2. The deadline — by when. (“Soon” is not a deadline. “By end of day Thursday” is.)
3. The owner — who is responsible. If you write to five people, name the one who owns the ask, or all five assume someone else has it.

Weak:   "Can someone take a look at the report at some point?"
Strong: "Priya — can you review the safety report and flag any gaps
         by 3pm Wednesday? I'll send the final version after that."

The strong version can’t be misread. There’s one owner (Priya), one action (review and flag gaps), one deadline (3pm Wednesday). No one else has to wonder if it’s their job.

The five-second test

Here’s a test you can run on anything you’re about to send. Can the reader tell, in five seconds, what you want them to know, feel, or do?

Read your own first sentence — just the first — and ask which of the three it delivers:

• Know — a fact or update. “The server migration finished overnight with no downtime.”
• Feel — a change in mood or confidence. “I want to reassure you: the outage is fully resolved and won’t recur.”
• Do — an action or decision. “Please approve the attached budget by Friday.”

If your first sentence delivers none of these — if it’s a warm-up, a “just following up,” a “hope you’re well and I was thinking” — you’ve failed the test. Rewrite the message so the answer is unmistakable in one line. Everything you learned here feeds forward: this discipline is what makes writing that gets read and speaking so people act possible.

Case study — Amazon’s six-page memo

Around the mid-2000s Amazon banned slide decks from many of its meetings in favor of six-page written memos, read in silence at the start of the meeting. Part of the reasoning, as leaders have described it, is that prose forces a clear line of argument in a way that bullet points can hide — a memo has to say something and defend it, in order. Whatever one thinks of the format, the underlying lesson holds: making people commit their point to a sentence, up front, exposes fuzzy thinking that bullets let you dodge. If you can’t state your point in one line, you may not have one yet.

Try this

Take the last three messages you sent that asked someone for something — an email, a chat message, a request. For each, underline your actual point (what you wanted them to know, feel, or do) and note where in the message it appeared. If it wasn’t in the first sentence, rewrite the opening line so it is — naming the ask, the deadline, and the owner where relevant. Then, for the rest of this week, run the five-second test on everything before you hit send.

Reflect

1. Think of a recent message where someone misunderstood what you wanted. Was the point in your first sentence — or did they have to hunt for it?
2. When you write, whose order do you tend to follow — the order you discovered things, or the order the reader needs them? What would change if you flipped it?
3. Where does the curse of knowledge bite you most — with your team, your boss, or people outside your field who don’t share your context?
4. Look at a message you sent recently. Did you lead with the topic (“about the schedule”) or the point (“please cover Saturday”)? How often do you confuse the two?
5. Which of your regular messages most often lack a named owner or a real deadline — and what goes wrong when they do?

Show reflections

1. Misunderstandings are usually a placement problem, not an intelligence problem. If the point was buried, the reader guessed — and the fix isn’t “explain more,” it’s “say it first.”
2. Most of us default to the discovery order because it’s how the thought felt. Flipping to the reader’s order costs a few seconds of editing and saves the reader (and you, in follow-ups) far more.
3. The curse bites hardest across a knowledge gap — with a boss who lacks the detail, or a customer who lacks the jargon. Naming your worst gap tells you where to over-explain the why while still leading with the point.
4. A strong answer catches yourself leading with topics and notices the pattern: topics feel like communication but commit to nothing. The test is whether your first line contains a verb the reader can act on.
5. Missing owners create “I thought you had it” gaps; missing deadlines create indefinite drift. If a recurring message keeps stalling, it’s usually one of these two — add the missing piece and watch it move.