"매 conclusion first, supporting reasons next, evidence last". Barbara Minto 의 McKinsey (1967) 의 develop 의 top-down structure 의 consulting/exec communication 의 standard. 매 reader 의 cognitive load 의 minimize — main idea 의 immediately 의 deliver.
매 핵심
매 Three Rules
Ideas at any level must summarize the ideas grouped below.
Ideas in each grouping must be the same kind (MECE — Mutually Exclusive, Collectively Exhaustive).
Ideas in each grouping must be logically ordered (time / structure / degree).
매 SCQA Intro Pattern
Situation: 매 reader 의 known fact.
Complication: 매 disrupt 의 event.
Question: 매 implicit question.
Answer: 매 thesis (= pyramid top).
매 응용
Exec memo — 매 1-page 의 BLUF (Bottom Line Up Front).
Consulting deck — 매 action title slide 의 each.
PR description — 매 "what / why / how" 의 top-down.
RFC docs — 매 abstract 의 conclusion-first.
💻 패턴
Bad → Good (technical email)
<!-- BAD: Bottom-up -->
We profiled the API. CPU was 80%. Then we added caching.
After caching, p99 dropped from 800ms to 120ms.
Therefore we should ship the cache to prod.
<!-- GOOD: Pyramid -->
**Recommend shipping Redis cache to prod (p99 800ms → 120ms).**- Profiling showed 80% CPU on repeated DB reads.
- Cache hit ratio 92% in staging.
- No correctness regressions in 48h soak test.
SCQA opener template
**S**: Our checkout API serves 10k req/s.
**C**: Last week, p99 spiked to 2s during flash sale.
**Q**: How do we prevent recurrence?
**A**: Add request-coalescing cache + circuit breaker. Details below.
Action-title slide structure
# [Slide title = the takeaway, not the topic]
# BAD: "Q3 Revenue Analysis"
# GOOD: "Q3 revenue grew 22% driven by enterprise tier"
- Bullet 1 (evidence)
- Bullet 2 (evidence)
- Bullet 3 (evidence)
PR description pyramid
## TL;DR
Fix race in `OrderQueue` causing lost messages under high load.
## Why
- Reproduced 1/1000 message loss in load test.
- Root cause: missing mutex in `enqueue()`.
## How
- Added `sync.Mutex` (commit a1b2c3).
- New stress test (commit d4e5f6).
## Risk
Low — change is local; backward compatible.
MECE grouping check
# Pseudo: ensure subpoints partition the parent claimparent="User churn increased"children=["Onboarding friction",# acquisition phase"Feature gaps",# activation phase"Pricing",# retention phase]# MECE: each is distinct phase, together cover funnel.
매 결정 기준
상황
Use pyramid?
Exec / time-poor reader
Yes — BLUF
Persuasive memo
Yes — SCQA
Narrative storytelling
No — suspense matters
Tutorial / step-by-step
No — sequence matters
Research paper abstract
Yes — conclusion-first
기본값: 매 business 의 technical writing 의 pyramid first.
Antigravity Agent
f8b21af4be