Best practice L2 · Context engineering informational

Lead With the Headline, Then the Detail

What it is

Structuring a summary so the single most important takeaway comes first — one line, the bottom line — followed by the key points, followed by supporting detail. The reader gets the conclusion immediately and descends into detail only as far as they need. It's the inverted pyramid, applied to AI summaries.

bottom line on topThe headline — bottom line in one lineread first3Key points — the supporting structureskim2Full detail — for those who need itread on demand1
Each layer lets the reader stop as soon as they have what they need.

Why it works

Most summaries make the reader do work to find the point — reading the whole thing to extract the one thing that matters. Leading with the headline flips that: the answer is in the first line, and everything after it is optional depth for those who want it. This respects that different readers need different amounts — a decision-maker may need only the top line, while someone acting on it needs the detail — and it front-loads the value so a summary that gets skimmed still delivers its core. Bottom-line-first is how you make a summary useful in the two seconds someone actually gives it.

When to use it

Any summary someone busy will read: status updates, briefs, research digests, meeting notes. Especially when the reader needs to decide fast whether to read further, or when the same summary serves both skimmers and deep readers.

When not to use it

Narrative or persuasive pieces where the payoff depends on building up to a conclusion — giving away the ending first would flatten them. Layered summaries are for information delivery, not for writing meant to be experienced in order.

Prompt

Summarise this in layers, bottom line first:
1. One sentence: the single most important takeaway.
2. Three to five bullet points: the key supporting facts.
3. A short 'detail' section for anyone who needs to go deeper.

Someone should be able to stop after line 1 and still have the essential point. Source: <paste or attach>.

Example

A project update opens: 'Bottom line: we'll miss Friday's deadline by about a week.' Then the bullets on why, then the detail on the recovery plan. The exec reads one line and knows what they need; the project lead reads the bullets; the person doing the recovery reads the detail. One summary, three depths, and the crucial fact isn't buried in paragraph four.

Advanced version

Pair the layering with audience-targeting: write the headline for the decision-maker and the detail layer for the doer, so the structure maps to the reading chain. And keep the headline honest — if the bottom line is 'it's complicated', say that rather than forcing a false crisp takeaway; a misleading headline is worse than a buried one.

Common mistakes

  • Burying the actual conclusion in the middle and opening with background — the classic 'read all of it to find the point' summary.
  • Writing a crisp headline that oversimplifies to the point of being wrong, just to satisfy the format.
  • Making every layer say the same thing at different lengths, instead of each adding real depth over the one above.

Related