The buried lede: why your point is three paragraphs down

A buried lede is the one sentence your reader needs, sitting three paragraphs below the place they would look for it. In work messages it is usually the last line, arriving right after the word "anyway". Move that line to the top and most of what sat above it turns out to be optional.

The advice everyone gives is to lead with your point. It fails for a dull reason: when you start typing you do not know your point yet, because writing is how you work it out.

So the job happens after the draft exists. One pass, looking for one thing.

Why the point ends up at the bottom

Your point lands at the bottom because you wrote in the order you thought of things, and your conclusion was the last thing you thought of.

A first draft is a transcript of the trip. What happened, what you checked, what you ruled out, and then, at the end, what you want. That order is honest and it is no use to a reader who joined at the destination.

There is a second reason and it is less flattering. Opening with the ask feels rude, so you lay out the evidence first, like a person defending themselves before anyone has made an accusation. By the time the ask shows up it reads as a footnote to your own case.

Nobody reads in your order. They read line one, decide what this message is, and scan the rest for confirmation.

How to find your own buried lede

Read your draft from the bottom up and stop at the first sentence that would change what the reader does.

That sentence is the lede. It is rarely the best written line in the draft. It is the one with a consequence attached.

Four checks, in order:

• Read only the last paragraph and ask whether it could open the message.
• Find the sentence that names an action, a decision, or a date.
• Cover the top half of the draft with your hand and see whether the reader actually loses anything.
• Say out loud what you want this person to do after reading, then use the sentence you said.

The last check is the one that still works when I am tired. Speaking is faster than hunting, and speech skips the throat clearing that a keyboard invites.

The words that sit right in front of it

Your buried lede almost always follows a hinge word, which means you can search for it instead of hunting for it.

• "Anyway" is the loudest signal there is, and the sentence after it is your message.
• "Basically" means you are about to say the thing you should have said first.
• "So I guess what I'm asking is" is the ask in a bad disguise.
• "Long story short" turns up after the long story, which is the wrong end of it.
• "The reason I'm writing" is a promise you could have kept in line one.
• A TL;DR at the bottom is a confession with a summary attached.

None of these are bad writing. They are the seams where thinking turned into a conclusion, and they are the most useful marks in the draft, because they show you the spot.

Move it, then cut what was holding it up

Put the lede in line one, then delete every sentence that existed only to walk the reader toward it.

Here is a message I have written versions of far too many times:

"Hi, hope the week is going okay. We picked up the export bug on Tuesday and it turned out to be the same date parsing problem from the old importer, which I thought had been fixed ages ago. There are two other tickets sitting on the same file. Anyway, I don't think Thursday is realistic for the release and I'd rather move it."

The rewrite is shorter, and it is warmer than it looks:

"I want to move the release from Thursday to Monday. The export bug is the old date parsing problem, and two other open tickets touch the same file. If Monday does not work, tell me by tomorrow morning and I will work out what we can cut."

Watch what happened to the background. It survived, at one sentence, behind the ask, which is where background belongs once the reader knows why they are being told about a file at all.

The greeting did not survive. That is a separate argument and I lose it with some people.

When I wrote the Unvent store listing, my first draft opened with why I built the thing, and the line explaining what it does was down in paragraph four. I had written a memoir and labelled it a description. If your buried lede is a question rather than a plan, the message wants the shape of a decision request instead.

When the lede should stay buried

Two situations justify the setup coming first, and they are narrower than the people defending them believe.

The first is a conclusion that sounds unhinged without one fact the reader does not have. "We should stop selling the thing that makes the money" needs its reason bolted on, or it reads as a joke and gets answered as one.

The second is when you want someone to change their mind rather than do a task. Open with the verdict and they start arguing with it while your reasoning is still queued behind, so disagreement has its own order.

Everything else is self-protection wearing the costume of context. A delay, or the request you know will annoy somebody, goes first. Bury one and the reader finds it in paragraph three, then rereads the two paragraphs above it wondering what else you softened.

One sentence of context is not a buried lede. If a clause makes the ask legible, keep the clause. The problem starts at a paragraph, then a second, then a third.

What to do with the paragraphs you cut

Keep them somewhere, because they are the answer to the question your reader is about to ask.

Most of what you strip out is the reply to "why?" and to "what did you try?". Paste it when those arrive, and enjoy how fast that reply goes out. Your last line then gets a job of its own, and a sign-off is not that job.

The second pass is the one that never happens on a busy afternoon. On those afternoons I take the Direct version in Unvent, which drags the ask toward the front before I have noticed it was hiding at the back.

I have stopped treating the ramble as a failure. The draft was doing its job, and the last line is the receipt for the thinking.

What I still get wrong is the send. The lede is sitting down there, I can see it, and some afternoons I decide the message is long enough already and ship the trip instead of the destination. Somebody replies asking what I actually want. I answer in one line, and that line was the message.