Lead With the Conclusion
There’s a convention in persuasive writing called “building the case”: lay out the context, walk through the evidence, then land the recommendation at the end once the reader has been brought along. It sounds rigorous. It fails in practice. By the time you reach the conclusion, half the people who needed to see it have stopped reading. The case you built so carefully was never received.
The distinction is between writing that builds to a position and writing that opens with one. Both can contain the same evidence. Only one puts the recommendation where the reader can find it. The first sentence sets context. The second sentence states the position. Everything after exists to defend it. That’s the structure, and it’s non-negotiable if you’re writing for people who have less time than you do, which is almost always.
Two axes expose the gap. The first is recommendation placement: where does your position appear? Bottom of the email, final slide of the deck, last paragraph of the memo. That’s the default. It feels earned. It isn’t. It’s a bet that the reader will read to the end. They won’t. The second axis is metric quality: are your numbers arguments or decoration? “Strong growth across the board” is decoration. “Revenue 22x in 8 quarters, $42K to $955K” is an argument. The test is simple: if the number were different, would the recommendation change? If not, cut it.
If you can’t write the conclusion first, you don’t have one yet. The discomfort of stating a position before the evidence is a signal that the thinking isn’t finished. The evidence should follow the position, not produce it.
The recommendation belongs in the second sentence, not the last paragraph. First sentence: context. Second sentence: position. The reader should be able to stop after two sentences and know what you’re asking them to do.
Make every number an argument. “Median wait fell from 15 seconds to 8 seconds while volume grew 8x” is a one-line proof. Flip the number, flip the recommendation. Anything that doesn’t clear that bar is filler.
Cut the preamble. “As we discussed last week, and given the context of the broader initiative” is throat-clearing. Start with the thing you need the reader to know.
The compound effect is reputational. The person whose writing always opens with the position gets read first and responded to fastest. People learn where to find the answer. You become the writer they open immediately.
Before you send, run these. Where is my recommendation, and can someone find it in the first two sentences? If a reader stopped after two sentences, would they know what I’m asking? Is every number I’ve included an argument, or is some of it decoration? Have I started with the conclusion, or am I still building to it?
One limit: sometimes the sequence matters for trust. If you’re delivering bad news or a recommendation the reader is predisposed to reject, leading with the conclusion can trigger defensiveness before you’ve established the reasoning. In those cases, a short setup that establishes shared ground first can make the recommendation land better. The principle still holds: get there fast. Just not always in the second sentence.
Put the recommendation first. Make the numbers earn their place. The rest is just defending the line you already drew.