Start with the point: the update format that gets read

Lead with your recommendation, then explain it. Most people write the way they think — context first, conclusion last — so the reader sits through the whole windup before learning what you actually want. Flip it. State the point in the first line; put the reasoning underneath. It's the single highest-leverage change you can make to how you're read.

The windup is costing you

When you save the recommendation for the end, you force a busy reader to reconstruct your thinking before they reach it. Some won't finish. Others will reply asking the question you were about to answer. Burying the point reads as indecision, even when you're sure.

Strong communicators do the opposite. Beginning, middle, end — but the beginning is the conclusion. This is sometimes called BLUF: bottom line up front.

Recommendation on top

The three-bullet update

For anything complex, structure beats prose. When you owe someone a decision, three bullets carry it cleanly:

1. Situation — one line on what's happening.
2. Recommendation — what you think should be done.
3. The ask — what you need from the reader, and by when.

If you can't reduce an update to those three, you don't yet know what you're asking for — which is exactly why the reader couldn't tell either.

How to start with the point

• Write the email, then move the last sentence to the top. The conclusion you drifted toward is usually the real opening.
• Begin with a verb of decision: "I recommend," "Let's," "We should," "Approve," "Hold off."
• Keep reasoning below the point, not in front of it. Context is support, not setup.
• One message, one point. If there are two decisions, send two messages — or label them clearly.

Structure is a habit you can drill. In the Sprint's structure week, you take real memos and rewrite them recommendation-first, then practice the three-bullet format on your own updates. Do it enough and leading with the point stops feeling unnatural — it becomes your default.