| 1 | # Mode: pyramid |
| 2 | |
| 3 | Conclusion-first argumentation. State the answer, then support it with structured evidence — every claim earns its place and data is contextualized without inventing comparisons. For audiences who want the result before the process: executives, boards, investors, decision-makers. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## 1. Narrative skeleton |
| 8 | |
| 9 | **Conclusion first**: the page title *is* the conclusion, not a label. The body develops the supporting arguments beneath it. |
| 10 | |
| 11 | SCQA opening, pyramid body: |
| 12 | |
| 13 | | Stage | Role | Where | |
| 14 | |---|---|---| |
| 15 | | Situation | establish shared context | opening pages | |
| 16 | | Complication | the tension / problem | early pages | |
| 17 | | Question | the implicit question to resolve | transition | |
| 18 | | Answer | the recommendation, developed through structured evidence; use MECE when the source supports it | body pages | |
| 19 | |
| 20 | **Assertion titles** — write the finding, not the topic: |
| 21 | |
| 22 | | Weak (topic) | Strong (assertion) | |
| 23 | |---|---| |
| 24 | | "Market Overview" | "Domestic market grows 23% YoY, outpacing the global average" | |
| 25 | | "Challenges" | "Three structural contradictions block scaled deployment" | |
| 26 | | "Our Solution" | "Three-phase path: Focus, Expand, Scale" | |
| 27 | |
| 28 | **Contextualize data** — pair a figure with a supported comparison when that comparison changes the decision; otherwise state its direct relevance or implication. Never invent a prior period, benchmark, competitor, target, or rank to satisfy the mode. |
| 29 | |
| 30 | **Structured decomposition** — when decomposing drivers, segments, or options, make branches meaningfully distinct and cover what the decision needs. Preserve real overlap or an acknowledged gap instead of fabricating a perfect MECE partition. |
| 31 | |
| 32 | --- |
| 33 | |
| 34 | ## 2. Page-structure tendencies |
| 35 | |
| 36 | - Title (the conclusion) → concise takeaway → supporting evidence beneath. |
| 37 | - Each body page centers on a decision-relevant question and states a clear conclusion; supporting subquestions may share the page when their relationship matters. |
| 38 | - Decomposition pages (driver tree / MECE breakdown / 2×2 matrix) carry the analytical load. |
| 39 | - Source attribution on every data page. |
| 40 | |
| 41 | > Page structure is a tendency, not a coordinate template. Card / tree / chart / KPI geometry lives in [`templates/charts/`](../../templates/charts/) — adapt those skeletons, do not reinvent. This mode decides *what argument each page makes*, not pixel positions. |
| 42 | |
| 43 | --- |
| 44 | |
| 45 | ## 3. Speaker-notes register |
| 46 | |
| 47 | Conclusion-driven: open each page's notes with the takeaway, then support it with a compact set of facts in flowing prose. Composed, authoritative. Pair a number with a supported comparison when it materially clarifies the takeaway ("23% — nearly double the industry's 12%"); otherwise explain its implication directly. Spell percentages as words where the spoken form reads more naturally. (Common framework: [`executor-notes.md`](../executor-notes.md) §1.) |
| 48 | |
| 49 | --- |
| 50 | |
| 51 | ## 4. Page skeleton example |
| 52 | |
| 53 | ``` |
| 54 | Title: "Retention, not acquisition, now drives growth" ← the conclusion |
| 55 | Takeaway: one line — "CAC up 40% YoY, yet repurchase lifted 60% of revenue growth" |
| 56 | Body: supporting arguments with contextualized data |
| 57 | Footer: Source: … | page # |
| 58 | ``` |
| 59 |