Lead With the Conclusion

A coworker sends you a 600-word email. Three paragraphs of context, two paragraphs of analysis, and finally, in the last sentence: "So I think we should pause the launch."

You missed it the first time. You had to scroll back up.

Most writing builds to the recommendation like a punchline. It doesn't work. The reader is skimming. The reader has six other tabs open. By paragraph two, half the people who needed to see your conclusion are gone.

Put the recommendation in the second sentence. The first sentence sets the context. The second sentence states the position. Everything after exists to defend it.

This sounds obvious until you try it. The discomfort is real: stating a position before the evidence feels like skipping the work. It's the opposite. It forces the work to be sharper. If you can't write the conclusion first, you don't have one yet. You have a pile of observations.

The numbers that defend the conclusion get the same treatment. Most metrics in most documents are decoration. "Strong growth across the board." "Engagement is up." None of those would change a decision if they were different.

Lead with numbers that are arguments. "Revenue 22x in 8 quarters, $42K to $955K." "Median wait fell 15s to 8s while volume grew 8x." Each one is a one-line proof: flip the number, flip the recommendation. Anything else is filler. Cut it.

The compound effect is reputation. The person whose memos open with the position gets read first. People learn the answer is in the first two sentences and the proof is in the next four. You stop being the writer people skim around. You start being the writer people open immediately.

This applies to emails, decks, retros, performance reviews, kickoff docs. Anywhere a position is being conveyed to a reader who will not give you their full attention.

Lead with the conclusion. Make the numbers earn their place. The rest is just defending the line you already drew.