Writing That Actually Gets Read

Lead With the Point (BLUF) taught you to put your conclusion in the first line, before the reasoning. This page takes that instinct and applies it to the whole shape of a written message — the paragraphs, the bullets, the length, the placement of the ask. Leading with the point tells you where the conclusion goes; this page tells you how to build everything around it so a distracted reader still leaves informed and knowing what to do.

Here is the uncomfortable truth this page is built on: almost nobody reads your writing the way you wrote it. You composed it top to bottom, weighing each word. They skim it in eight seconds between two meetings, on a phone, half-listening to someone else. Writing that gets read is writing designed for that reader — not the ideal, attentive one you imagined, but the real, busy, skimming one you actually have.

The principle: assume the reader is skimming, not studying

You are not writing to be admired. You are writing to transfer a decision, a status, or an instruction into someone else’s head, and then to get them to act. That is the only job. Every rule below serves it.

The reader’s attention is the scarce resource, not your effort. A message that took you thirty minutes to write but takes the reader two minutes to decode has failed, no matter how careful it was. The measure of good writing at work is not “did I say everything?” — it’s “did the right thing land, fast, in a busy mind?”

So design for skimming. Assume the reader’s eyes will jump — to the first line, to anything bold, to the bullets, to the bottom — and skip the rest. Your job is to make sure that even a pure skim leaves them correctly informed. If the only way to get the point is to read every word, most people will get the point wrong, or not at all.

This flips the usual instinct. Most of us write to feel thorough — to prove we did the thinking, covered the angles, left nothing out. But the reader doesn’t reward thoroughness; they reward speed of understanding. A message optimized for the writer’s peace of mind is almost always the wrong shape for the reader’s eight-second scan. When those two pull in opposite directions, the reader wins, because the reader is the one who has to act.

The evidence — nobody reads to the end

Studies of how people read on screens generally find the same pattern: readers scan in an F-shape, reading the top lines fully, then dropping down the left edge and sampling less and less. Attention to a page tends to fall off sharply after the first screen. The practical takeaway is not a precise number — it’s the direction: the further down the page something sits, the less likely it is to be read at all. Load-bearing content belongs at the top.

Structure for scanning

A wall of text tells the reader nothing about where to look, so they look nowhere. Structure is how you guide a skimming eye to the parts that matter.

Headline first. Give the message a one-line summary at the very top — the subject line, the first sentence, or a bold lead. It should carry the whole point on its own. “Launch is slipping to the 14th — need your sign-off by Thursday” is a headline. “Following up on our conversation” is not.

Short paragraphs. Two to four lines each, one idea per paragraph. A paragraph that fills the screen reads as “skip me.” White space is not wasted space — it’s the runway the eye lands on.

Bullets for lists. Anything that is a set of items — options, steps, risks, updates — becomes a bulleted or numbered list, not a comma-stuffed sentence. Lists are scannable; sentences full of “and… and… and…” are not.

Bold the decision or the ask. The one thing the reader must not miss gets visual weight. Use it sparingly — if everything is bold, nothing is. One bolded ask per message is usually right.

Compare the same update, unstructured and structured:

BEFORE (a wall):
Hi all, I wanted to give everyone a quick update on where things
stand with the onboarding project since we last spoke, there's been
a fair bit of movement and I know a few of you had questions about
timing so I figured I'd get everything down. We've finished the
first two screens and testing went okay although we found a couple
of issues with the payment step which we're still looking into and
that might affect the date, also legal hasn't come back yet...

AFTER (structured):
Onboarding update — on track except payments; need a decision on the date.

Done:
- First two screens built and tested.

Blocked:
- Payment step has two open bugs (fix ETA Wednesday).
- Legal review still pending.

**Ask: can we hold the launch date to the 14th, or should I move
it to the 21st? Please reply by Thursday.**

Same information. The second version can be understood in a five-second skim; the first cannot be understood at all without a careful read most people won’t give it.

In practice — the shift-handover note

On a hospital ward, a nurse handing over at end of shift doesn’t write a paragraph about how the day went. They write a structured note: patient, status, what changed, what the next shift must watch for. The structure isn’t bureaucracy — it’s because the incoming nurse is tired, busy, and scanning, and a buried detail is a missed detail that can hurt someone. The same discipline that keeps a ward safe makes an ordinary work update actually usable.

Ruthless brevity: every sentence earns its place

Shorter is not lazier. Shorter is harder to write and easier to read, which is exactly the trade you want. Length feels thorough to the writer and feels like a wall to the reader.

Three things to cut without mercy:

Throat-clearing. The warm-up sentences before the point. “I hope you’re well. I wanted to reach out because I’ve been thinking about…” Delete all of it and start at the point. The reader will not feel you were abrupt; they will feel you respected their time.

Hedging. “I might be wrong, but it seems like perhaps we could maybe consider…” Every hedge shaves confidence off your message and adds words. Say the thing. If you’re genuinely unsure, say that plainly (“I’m about 70% sure of this”) — one clear hedge beats five vague ones.

Redundant context. The reader was on the call; they don’t need it recounted. They know what the project is; you don’t need to reintroduce it. Give only the context that a specific reader specifically lacks.

A useful test: read each sentence and ask, “If I deleted this, would the reader be worse off?” If the answer is no, delete it. Do this on every draft and most messages shrink by a third — and improve.

Brevity is mostly an editing act, not a drafting one. Write the messy first version to get your own thinking straight — that’s fine, nobody sees it. Then edit it down for the reader. The gap between “what I needed to write to think” and “what you need to read to act” is exactly the material you cut. Skipping the edit is the single most common reason clear thinkers send unclear messages: the draft that helped them understand gets shipped to a reader who needed something much tighter.

In practice — the cafe owner’s supplier email

A cafe owner needs to change a standing coffee-bean order. The first draft explains the seasonal menu, last month’s foot traffic, and a supplier conversation from March. The edited version is three lines: current order, new order, start date. The supplier doesn’t care why; they care what to ship and when. The context that felt important to write was invisible to the reader’s actual task. Brevity here isn’t rudeness — it’s aiming the message at what the reader has to do.

The common trap — mistaking length for thoroughness

Many people believe a long message proves they were careful, and a short one looks sloppy or curt. It’s backwards. The long message pushes the work of finding the point onto the reader; the short one does that work for them. A five-line email that lands cleanly is more respectful and more effective than a two-page one that buries the same point. If you fear seeming curt, spend your words on warmth (“thanks for turning this around”), not on padding — warmth is short, and padding never was.

Make the action unmissable

The most common failure in workplace writing is not a wrong message — it’s a lost ask. The writer knew what they needed. The reader finished the message and had no idea what they were supposed to do, so they did nothing.

An action that a reader can act on has three parts, and all three must be visible:

- The ask:      exactly what you need done
- The owner:    who is supposed to do it (a name, not "someone")
- The deadline: by when (a date, not "soon" or "when you get a chance")

Put all three together, in one place, bolded, near the top or clearly at the end — never buried in the fourth paragraph where a skimmer will sail right past it. “Priya — please approve the budget by Friday the 11th” is unmissable. “It would be great if we could sort out the budget situation at some point” is not an ask; it’s a wish, and wishes don’t get done.

If a message has no action at all — it’s purely informational — say that too: “No action needed, just keeping you in the loop.” That single line saves every reader from scanning anxiously for a hidden task.

And when a message has several asks for several people, don’t rely on each person to find their own line in the crowd. Group the actions by owner, or tag each name directly, so no one can honestly say “I didn’t realize you meant me.” The more people a message reaches, the more the responsibility diffuses — a warehouse shift-lead who addresses “the team” gets slower results than one who writes “Sam, you take receiving; Dana, you take dispatch.” Named owners act; unnamed crowds assume someone else will.

Match length to purpose

There is no universal right length. There is a right length for each purpose, and using the wrong one is its own kind of failure. A novel-length Slack message and a one-line answer to a decision that needed a document are both mismatches.

Purpose                         Right size
-----------------------------   --------------------------------
Quick question or nudge         One line (chat)
Status update, simple request   3–6 lines (email/chat)
Proposal, decision, analysis    A structured doc with headings
Anything with real stakes       Long enough to be complete,
                                 short enough to be read

The mistake runs both ways. Cramming a real decision — with trade-offs, risks, and a recommendation — into a one-line chat message forces a scattered discussion that could have been settled by one good document. And stretching a simple “can you approve this?” into six paragraphs buries the ask and wastes everyone’s time. Ask first: what is this message for? Then pick the size that fits.

Case study — Amazon’s six-page memo

In the early 2000s, Amazon banned slide decks in many of its meetings in favor of narrative memos — famously capped at around six pages — read silently at the start of the meeting. Jeff Bezos’s reasoning, described in later shareholder letters, was that writing full sentences forces clearer thinking than bullet points can hide: you can fake understanding with a slide, but not with a paragraph that has to hold together. The lesson isn’t “always write six pages” — most messages should be far shorter. It’s that the form should match the stakes: a real decision deserves prose that forces real thought, and the length should be set by the purpose, never by habit.

Write for both readers at once

Every message has two readers hiding inside every real one:

• The first-line reader, who reads only the headline and moves on.
• The every-word reader, who reads the whole thing carefully.

Good writing serves both without choosing. The first-line reader must get the core message from the top alone — the headline and the bolded ask. The every-word reader must find the supporting detail, the reasoning, and the nuance below, in the order they’d want it.

This is why structure and brevity aren’t in tension. The tight headline serves the skimmer; the structured detail below serves the careful reader; and because it’s structured, the careful reader can still skim to the part they need. You are not writing one message for an imagined average reader — you’re layering it so the skimmer and the studier both leave correctly informed. When both can act correctly on the same message, you’ve written something that actually gets read.

A quick way to test any draft against both readers: cover everything below the first line and ask whether a skimmer would still know the point and the ask. Then read the whole thing and ask whether the careful reader has what they need to act without replying to ask you a follow-up question. If both pass, the message is done. If the skimmer would be lost, your headline is too weak; if the careful reader would have to write back, your detail is too thin. Most workplace writing fails one of these two tests — and the writer usually can’t tell which, because they wrote it and already know the answer. Testing the draft as if you didn’t is the whole skill.

How it connects

This page is the written half of a pair. Speaking So People Act does the same work out loud, where you can’t bold a word but you can pause, repeat, and read a face. Choosing the Channel helps you decide when a thing should be written at all versus said, and when it should be async versus live. And every rule here rests on Lead With the Point: the headline you put first is the point you led with.

Try this

Take one message you sent this week that was longer than five lines — an email or a long chat. Rewrite it under three constraints: (1) a one-line headline at the very top that carries the whole point, (2) any list turned into bullets, and (3) the ask, owner, and deadline bolded in one place. Then delete every throat-clearing and hedging sentence. Count the lines before and after — most people cut a third — and notice whether the shorter version is actually clearer. Send messages this way for a week and watch how much faster you get replies.

Reflect

1. Think of a recent message you sent where the reader missed your ask or replied to the wrong part. Was the ask buried, hedged, or missing an owner and deadline?
2. When you write, are you picturing the real skimming reader — on a phone, between meetings — or an idealized one who reads every word carefully?
3. Which do you personally overuse: throat-clearing intros, hedging language, or redundant context? What would change if you cut it?
4. Recall a time you crammed a real decision into a quick chat message, or stretched a simple ask into a long one. What was the cost of the mismatch?
5. Does a short message feel curt or sloppy to you? Where does that belief come from, and is it serving your readers or just your own comfort?

Show reflections

1. The goal is to trace a real failure back to its cause. Most missed asks come from one of three fixable faults: the action was buried below the fold, it was hedged into a wish, or it named no owner and no date. Naming which one lets you fix the next message deliberately.
2. This is the core mindset shift. If you picture the ideal reader, you write walls; if you picture the real one, you write headlines and bullets. Honest answers usually reveal we write for the reader we wish we had.
3. Everyone has a signature filler. Spotting yours is high-leverage because it recurs in every message. Cutting it typically makes you sound more confident and competent, not less — the opposite of what the habit fears.
4. Connect the mismatch to a concrete cost: a scattered thread, a decision that dragged for days, a reader who tuned out. The lesson is that size is a choice tied to purpose, not a default — and the wrong size has a real price.
5. This belief drives a lot of padding. A strong answer separates warmth (which is worth keeping and is short) from length (which is not thoroughness). Curtness is a tone problem, solved with a kind line — not a word-count problem.