Write Like the Reader Is in a Hurry

There’s a principle in writing: “the reader is always right.” Most people interpret that as “know your audience.” The real insight is harder. The reader won’t tell you when they got confused, when they gave up, or when they misunderstood and acted on it anyway. You’ll never see the moment they closed the tab. Which means every point of friction you don’t eliminate yourself will silently kill your document, your recommendation, or your credibility, and you won’t know it happened.

Most writing pretends the reader has time. They don’t. Your boss opens your doc on her phone between meetings, with six other tabs behind it. She is going to skim, hit the first thing that slows her down, and move on. Writing that doesn’t account for this isn’t just inefficient. It’s a bet that the reader will do the work you didn’t do. They won’t.

Two axes expose the gap. The first is caveat handling: do you bury the weaknesses or volunteer them? Buried caveats feel safer. They’re not. The moment a reader finds something you could have told them, your credibility on everything before it collapses. Volunteered, the same caveat becomes a signal that you thought it through. “Q2 is in-progress, totals will look low until June” is one sentence that protects the rest of the document. The second axis is audience layering: are you writing for one undifferentiated reader, or are you structuring for two? The skimmer wants the recommendation and the proof in 30 seconds. The auditor wants the methodology and the definitions in 30 minutes. Most writers pick one and lose the other. Both are in the room.

Put the recommendation in the second sentence. First sentence: context. Second sentence: position. Everything after: defense. If you build to the conclusion like a punchline, half your readers are gone before they find it.

Volunteer the wart before the reader finds it. Whatever the most damaging caveat is, surface it early. Buried, it destroys trust. Volunteered, it actually protects the argument.

Pre-empt friction. “Give it 30 seconds to load.” “Skip section C if you’re short on time.” “Default filter is today, set it to your cutoff date.” These aren’t throat-clearing. They’re the difference between a document that gets used and one that gets closed.

Layer for two readers: position up top, evidence in the middle, methodology and definitions in an appendix. One document, two readers, both served.

Every metric should be an argument. “Strong growth across the board” doesn’t change a decision. “Revenue 22x in 8 quarters, $42K to $955K” does. If the number being different wouldn’t change your recommendation, it’s decoration. Cut it.

Here’s the same email written both ways.

Without these principles: “Hi team, as you know, we’ve been running the Q2 paid campaign for six weeks. We pulled data across all channels and compared it against last quarter. It’s worth noting that the dataset excludes organic traffic, so the numbers only reflect paid. After reviewing everything, we think the budget should be reallocated to SEO.”

The reader has to get to the last sentence to find the decision. The caveat about organic traffic is buried mid-paragraph, easy to miss. There’s no sense of what to do with this information.

With these principles: “Recommendation: reallocate the Q2 paid budget to SEO. Note: this analysis covers paid channels only, organic excluded. Six weeks of data across all paid channels shows declining return. Full breakdown below.”

Same information. The reader knows the recommendation in the first sentence, the caveat in the second, and whether to keep reading by the third. The person who skims gets what they need. The person who audits knows where to look.

Before you publish, ask these. Where is my recommendation, and can someone find it in the first two sentences? What’s the most damaging caveat, and have I surfaced it? Is there a “wait, how do I read this?” moment, and have I pre-empted it? Have I structured this for both the skimmer and the auditor?

One limit: some writing requires the reader to read carefully. Legal documents, safety instructions, compliance reviews. In these cases, friction isn’t a failure. But even then, the principles of clarity and layering apply. The difference is you’re not optimizing for speed. You’re optimizing for complete understanding with no room for misreading.

Most writing assumes the reader has time. Write as if they don’t. They don’t.