Yueser ← Back to library

AI / Office & Communication

Reporting Upward

Conclusion first, then the evidence and the risk

I need to report [topic] to [audience]. Write it in pyramid structure: 1) first sentence gives the conclusion; 2) three points that support it (one sentence plus one data point or fact each); 3) risks and how I'll handle them; 4) the decision I need from them. No background preamble unless I explicitly ask for it.

[Background material]
How to use

If the first sentence can't stand alone as the answer, the structure isn't done yet.

Good for

  • You are briefing an executive or client who does not know the details on a conclusion you have already reached; they have five minutes and need to decide in the room.
  • The material goes to cross-functional decision-makers ahead of time, and they need the conclusion, the evidence, and the ask without opening the attachment.

Not for

  • The conclusion is not formed yet and you need the other person to explore with you — the pyramid packages your early guess as a verdict and shuts down discussion.
  • The audience is the people doing the work; they need steps, dates, and a contact, not a conclusion and a risk list.

Example

Input
I need to brief the VP on building our own CDN versus staying with the cloud vendor. Bandwidth costs CNY 420k a month now; building is CNY 3M one-off plus CNY 80k a month in ops, payback around 14 months, but it needs 2 ops headcount we cannot hire until Q4.
What you get
The first sentence is the recommendation: stay on the cloud vendor through Q4, revisit self-hosting after. Three supporting points each carry a number — CNY 420k a month, 14-month payback, the 2-headcount gap — followed by the risks (vendor price hike, build delay) and how you would handle each. Close with a single ask: approve the two headcount in the budget by the end of October.

Common mistakes

  • Opening with industry trends and project background — five minutes in, the decision-maker still does not know what they are deciding, and reads it as unclear thinking.
  • Writing the ask as 'please support the team' — they do not know what to approve, how much, or by when, and the meeting decides nothing.

Try tweaking it like this

  • Add 'Also give me a one-minute version with only the conclusion and the ask', so the same material works for the opening and for the follow-up email.
  • Add 'Give the strongest opposing argument to the conclusion and why I am not taking it', for decision meetings where you will be challenged.

More in this topic