STRUCTURED COMMUNICATION · PRACTICAL GUIDE

Pyramid Principle: Make Complex Ideas Clear

Give your audience the answer first, then make the supporting reasons easy to follow, test, and act on.

Quick answer

State the main conclusion first. Support it with a small number of grouped, logically ordered reasons.

The method improves communication; it does not make a weak conclusion true. Facts and evidence still determine whether the answer is sound.

The four working rules

1. Lead with the conclusion

Answer “so what?” before giving the history.

2. Summarize from above

Every higher-level statement should summarize the ideas beneath it.

3. Group related ideas

Put ideas with a common property together and name that property.

4. Order ideas logically

Use time, structure, or importance to create a deliberate sequence.

Case study: reporting a project delay

A payment launch is due July 20. A vendor delivered four days late, two high-priority refund defects remain, and a July 22 campaign depends on launch.

Chronological update

“Last week we finished payments, then the vendor was late, testing found refund issues, and the team has been fixing them...”

The audience must infer the decision.

Pyramid update

“Delay launch five days to July 25 and move the campaign with it.”

Three reasons support this: compressed testing, unresolved refund defects, and launch risk greater than delay cost.

Conclusion: delay five days.
  • Schedule: vendor delay compressed testing.
  • Quality: two critical refund defects remain.
  • Risk: a rushed launch may create financial errors and complaints.

Copy-ready templates

Briefing outline

CONCLUSION / RECOMMENDATION
We recommend ______ by ______.

REASON 1: ______
- Evidence: ______
- Why it supports the conclusion: ______

REASON 2: ______
- Evidence: ______
- Why it supports the conclusion: ______

NEXT ACTION
Owner: ______  Deadline: ______  Decision needed: ______

Work email

Subject: Decision needed: move payment launch to July 25

Recommendation: Move launch and the related campaign by five days so the team can fix refund defects and run a complete regression test.

Why: the vendor delay compressed testing; two high-priority defects remain; launching now creates material financial and customer risk.

Request: Product, Engineering, and Marketing owners confirm by 5:00 p.m. today.

Checklist before you send

  • Is the audience and required decision clear?
  • Does the opening state the conclusion?
  • Does every lower-level point support the statement above it?
  • Are ideas grouped by one consistent rule?
  • Is the order based on time, structure, or importance?
  • Are facts separated from judgments?
  • Is there a clear owner, deadline, or request?
Connection to MECE: MECE improves the horizontal grouping within each level. The Pyramid Principle turns those clean groups into a vertical argument.