Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/17-DAAF-Contribution-Community-daaf/dot-claude/skills/science-communication

science-communication

Verified

Translating technical findings for non-technical audiences. Narrative frameworks (Pyramid Principle, SCQA), plain-language translation, executive summaries, policy briefs, causal language. Use when presenting to stakeholders or reviewing deliverables

references/narrative-frameworks.md

View on GitHub
# Narrative Frameworks

Six proven structures for organizing data-driven communication. Each framework serves a different purpose — the right choice depends on your audience, your goal, and the nature of your finding.

The key insight behind all of these: data alone does not persuade. As Brent Dykes argues, data, narrative, and visuals form a triad where all three must work together. Data provides the evidence, narrative provides the meaning, and visuals provide the intuition.

## Framework Selection Guide

Use this table to choose the right framework before you start writing:

| Framework | Best For | Audience | Key Strength |
|-----------|----------|----------|-------------|
| **Pyramid Principle** | Delivering recommendations | Executives, busy decision makers | Gets to the answer immediately |
| **SCQA** | Framing a problem that needs solving | Policymakers, funders, strategists | Creates urgency and motivation |
| **Three-Act Data Story** | Presenting a discovery journey | Mixed audiences, presentations | Builds engagement through narrative tension |
| **"So What?" Framework** | Translating findings into implications | Any audience that needs to act | Forces every finding to carry its weight |
| **Data-Narrative-Visual Triad** | Comprehensive stakeholder reports | Report readers, presentation audiences | Ensures nothing is missing from the communication |
| **AIDA** | Persuading stakeholders to invest or act | Decision makers resistant to change | Optimized for buy-in and commitment |

### Decision Tree

```
What is your primary goal?
├─ Deliver a recommendation or answer
│   ├─ Audience is time-constrained → Pyramid Principle
│   └─ Need to build the case first → SCQA
├─ Tell the story of a discovery
│   ├─ Findings were surprising or counterintuitive → Three-Act Data Story
│   └─ Findings confirm expectations but need action → "So What?" Framework
├─ Create a comprehensive deliverable
│   └─ Data-Narrative-Visual Triad (use as a completeness check)
└─ Persuade someone to commit resources
    └─ AIDA
```

---

## 1. Pyramid Principle (Minto)

**Origin:** Barbara Minto at McKinsey & Company. The gold standard for business and consulting communication.

**Core idea:** Start with the answer. Then provide supporting arguments. Then provide evidence for each argument. The reader should be able to stop at any level and have a complete (if less detailed) understanding.

### Structure

```
Level 1: ANSWER (one sentence)
  ├─ Level 2: Supporting Argument 1
  │   ├─ Level 3: Evidence A
  │   └─ Level 3: Evidence B
  ├─ Level 2: Supporting Argument 2
  │   ├─ Level 3: Evidence C
  │   └─ Level 3: Evidence D
  └─ Level 2: Supporting Argument 3
      ├─ Level 3: Evidence E
      └─ Level 3: Evidence F
```

### Rules

1. **Start with the answer.** The very first sentence of the deliverable states the conclusion or recommendation. Not the background, not the methodology, not the context — the answer.
2. **Group supporting arguments logically.** Three arguments is ideal (human working memory). Each argument must independently support the answer.
3. **Arguments before evidence.** A busy reader reads Level 1 and Level 2. Only interested readers drill into Level 3.
4. **MECE at each level.** Arguments should be Mutually Exclusive and Collectively Exhaustive — no gaps, no overlaps.
5. **Use vertical and horizontal logic.** Read top-to-bottom (each level supports the one above) and left-to-right (arguments at the same level are parallel in structure).

### Example Skeleton

> **Answer:** School districts should prioritize early literacy interventions over class-size reduction to improve reading outcomes.
>
> **Argument 1:** Early literacy programs show 2-3x larger effect sizes than class-size reduction in controlled studies.
> - Evidence: Meta-analysis of 47 RCTs...
> - Evidence: Our district-level analysis confirms...
>
> **Argument 2:** Early literacy interventions are more cost-effective per student served.
> - Evidence: Cost-per-student comparison...
> - Evidence: Scalability analysis...
>
> **Argument 3:** Implementation is faster and less politically complex.
> - Evidence: Timeline comparison...
> - Evidence: Stakeholder survey results...

### When to Use

- Executive summaries and recommendations
- Board presentations
- Any situation where the audience's first question is "What should we do?"
- When you have limited time or space

### When NOT to Use

- When the audience needs to be convinced the problem exists before hearing the answer
- When the finding is politically sensitive and needs careful framing
- When the journey of discovery is itself the story

---

## 2. SCQA (Situation-Complication-Question-Answer)

**Origin:** Also from Barbara Minto, as a setup technique for the Pyramid Principle. Widely used in consulting and policy communication.

**Core idea:** Before giving the answer, establish *why the audience should care* by framing a problem. SCQA creates the cognitive "itch" that the answer then "scratches."

### Structure

| Element | Purpose | Example |
|---------|---------|---------|
| **Situation** | Establish shared understanding of the status quo | "School districts have increased spending on class-size reduction for two decades." |
| **Complication** | Introduce the tension, problem, or surprising finding | "Despite this investment, reading proficiency has not improved — and in some districts, it has declined." |
| **Question** | State the question the audience is now asking | "What intervention strategies actually improve reading outcomes?" |
| **Answer** | Deliver the finding or recommendation | "Our analysis of 200 districts shows that early literacy programs produce 2-3x the effect of class-size reduction at lower cost." |

### Rules

1. **Situation must be uncontroversial.** The audience should nod along — "yes, that's the world I know." No new information here.
2. **Complication creates tension.** It disrupts the comfortable situation. This is where the energy comes from.
3. **Question must feel inevitable.** If the complication is well-crafted, the audience is already asking the question before you state it.
4. **Answer resolves the tension.** It should feel satisfying — the puzzle pieces fit together.

### When to Use

- Policy briefs where you need to motivate the reader before presenting findings
- Funding proposals where you need to establish the need
- Any situation where the audience doesn't yet recognize the problem
- When your findings challenge the conventional wisdom

### When NOT to Use

- When the audience already knows the problem and just wants the answer (use Pyramid)
- When the situation is too complex for a brief setup

---

## 3. Three-Act Data Story

**Origin:** Classical dramatic structure (Aristotle's Poetics) applied to data communication. Championed by Brent Dykes and Cole Nussbaumer Knaflic.

**Core idea:** Treat your analysis as a narrative with setup, conflict, and resolution. This structure works because human brains are wired for stories — narrative activates more brain regions than data alone.

### Structure

| Act | Name | Data Story Purpose | Content |
|-----|------|--------------------|---------|
| **Act 1** | Setup | Establish context and expectations | What is the baseline? What would we expect to see? What does "normal" look like? |
| **Act 2** | Confrontation | Reveal the surprise, tension, or insight | What did the data actually show? Where does reality diverge from expectation? What is the "aha" moment? |
| **Act 3** | Resolution | Deliver implications and next steps | What does this mean? What should change? What questions remain? |

### Rules

1. **Act 1 must be brief.** Don't spend half the presentation on background. Set the stage quickly — the audience came for Act 2.
2. **Act 2 is the star.** The data insight is the turning point. Make it vivid, specific, and surprising. This is where your best visualization goes.
3. **Act 3 must be actionable.** Don't end with "more research is needed" unless that is genuinely the most important takeaway. End with what the audience can *do*.
4. **One story per deliverable.** If you have three insights, tell three stories — don't weave them into one confused narrative.

### Example Skeleton

> **Act 1 (Setup):** Between 2015 and 2020, our district invested $14M in class-size reduction, bringing the average from 28 to 22 students per class. The expectation was measurably improved reading scores.
>
> **Act 2 (Confrontation):** Reading proficiency remained flat — and in 12 of our 18 schools, it actually declined. Meanwhile, three schools piloting early literacy programs with a fraction of the budget saw double-digit gains.
>
> **Act 3 (Resolution):** The evidence suggests that how instructional time is used matters more than class size. We recommend redirecting $8M toward structured literacy programs while maintaining current class sizes.

### When to Use

- Presentations to mixed audiences
- When the finding is surprising or counterintuitive
- When you need to take the audience on a journey to appreciate the conclusion
- Conference talks and public lectures

### When NOT to Use

- When the audience is impatient and wants the answer immediately (use Pyramid)
- Written deliverables for busy executives (the "story" wastes their time)

---

## 4. "So What?" Framework

**Origin:** A practitioner framework common in consulting, journalism, and science communication. Each finding must answer "so what?" before it earns inclusion.

**Core idea:** Every finding in your deliverable must carry three layers: the finding itself, its implication, and the action it suggests. If a finding can't answer "so what?" at all three levels, it doesn't belong.

### Structure

For each finding:

```
Finding → Implication → Action
  "What did we observe?"
    → "Why does this matter?"
      → "What should someone do about it?"
```

### Example

| Layer | Content |
|-------|---------|
| **Finding** | Students in high-poverty districts are 3x less likely to have access to AP courses. |
| **Implication** | This creates a compounding disadvantage: fewer AP courses → fewer college credits → higher college costs → lower completion rates. |
| **Action** | State funding formulas should include AP course access as a weighted factor for high-poverty districts. |

### Rules

1. **Apply the "so what?" test to every finding.** If a finding is interesting but has no implication or action, it belongs in an appendix, not the main text.
2. **The implication is where you add value.** Anyone can report what the data shows. Explaining what it *means* is the analyst's contribution.
3. **Actions should be proportional to evidence.** Strong evidence supports specific recommendations; weaker evidence supports "areas for further investigation." Match the action to the inferential capacity (see `plain-language.md` on causal language).
4. **Layer the full chain for your most important findings.** Minor findings may stop at the implication level.

### When to Use

- As an editing filter for any deliverable (apply to every paragraph — does it answer "so what?")
- Reports that combine multiple findings
- When your audience is action-oriented
- As a completeness check: if you can't state the implication, you may not understand your finding well enough

### When NOT to Use

- This is more of a universal editing tool than a standalone structure. It works *within* other frameworks rather than replacing them.

---

## 5. Data-Narrative-Visual Triad (Dykes)

**Origin:** Brent Dykes, *Effective Data Storytelling* (2019).

**Core idea:** Effective data communication requires all three elements — data, narrative, and visuals — working together. Missing any one creates a deficiency:

| Combination | Missing Element | Result |
|-------------|-----------------|--------|
| Data + Narrative (no visuals) | Visuals | The audience must imagine the patterns — less intuitive, harder to remember |
| Data + Visuals (no narrative) | Narrative | The audience sees the chart but doesn't know what it means or what to do — "nice chart, so what?" |
| Narrative + Visuals (no data) | Data | Persuasive but ungrounded — decoration without evidence |
| **Data + Narrative + Visuals** | **Nothing** | **Complete communication — evidence, meaning, and intuition aligned** |

### Rules

1. **Data provides the evidence.** It must be rigorous, well-sourced, and correctly analyzed. (This is covered by data-scientist skill — not duplicated here.)
2. **Narrative provides the meaning.** It explains *why* the data matters, *what* the audience should take away, and *what* should happen next. Use one of the other frameworks in this file to structure the narrative.
3. **Visuals provide the intuition.** A well-designed chart makes the pattern *feel* obvious. (Chart construction is covered by data-scientist visualization references — not duplicated here.)
4. **All three must tell the same story.** If the chart shows one thing, the narrative says another, and the data supports a third, the communication fails.

### When to Use

- As a **completeness check** for any deliverable: Do I have the data? Have I explained what it means? Have I shown it visually?
- When reviewing someone else's work: identify which element is missing
- When planning a report or presentation: ensure all three are planned from the start

### When NOT to Use

- This is a meta-framework, not a structure. It tells you *what* must be present, not *how* to organize it. Pair it with another framework for structure.

---

## 6. AIDA (Attention-Interest-Desire-Action)

**Origin:** Marketing and persuasion framework, attributed to E. St. Elmo Lewis (1898). Adapted for data communication in contexts requiring stakeholder buy-in.

**Core idea:** Move the audience through four psychological stages — from noticing, to caring, to wanting, to committing.

### Structure

| Stage | Purpose | Data Communication Application |
|-------|---------|-------------------------------|
| **Attention** | Capture focus | Lead with a striking statistic, unexpected finding, or compelling comparison. "Students in our district spend 40% less time on reading instruction than the national average." |
| **Interest** | Sustain engagement | Develop the context. Show the pattern in the data. Provide the narrative that explains why this matters. |
| **Desire** | Create motivation to act | Present the solution and its evidence. Show what success looks like elsewhere. Quantify the opportunity cost of inaction. |
| **Action** | Secure commitment | Make the ask specific and achievable. "We recommend a $2M pilot program in 6 schools for the 2026-27 school year." |

### Rules

1. **Attention must be earned in the first sentence.** If you lose them here, nothing else matters.
2. **Interest requires narrative, not more data.** Data captured attention; now explain what it means with a story or analogy.
3. **Desire requires evidence of feasibility.** "Here's what happened when District X tried this approach." Comparable examples are more persuasive than theoretical arguments.
4. **Action must be concrete.** "Consider our findings" is not an action. "Approve the pilot budget" is.

### When to Use

- Budget presentations and funding requests
- Change management communications
- When the audience needs to be persuaded, not just informed
- When inaction is the default and you need to overcome it

### Example Skeleton

> **Attention:** "For every dollar we spend on class-size reduction, we get 15 cents of reading improvement. For every dollar we spend on structured literacy, we get 42 cents."
>
> **Interest:** Over the past six years, we tracked 200 districts that took different approaches to improving reading. The pattern was consistent across rural, suburban, and urban settings: the *type* of instructional investment mattered far more than class size. Three schools in our own district piloted literacy programs and saw double-digit gains — while our $14M class-size investment produced flat results.
>
> **Desire:** District X, which is demographically similar to ours, switched to structured literacy three years ago. Their proficiency rates have climbed from 52% to 71%. Their per-student cost dropped by 40%. And their largest gains came from the students who were furthest behind — exactly the population we're most concerned about.
>
> **Action:** We are requesting Board approval for a $2M pilot across 6 schools starting fall 2026, with an independent evaluation reporting interim results in January 2027. The pilot is designed to produce evidence sufficient for a district-wide decision by spring 2027.

### When NOT to Use

- Academic publications (AIDA is persuasive; academic communication should be neutral)
- When the audience is already motivated and just needs information
- When the action is unclear or premature — don't force an ask that isn't ready

---

## Combining Frameworks

These frameworks are not mutually exclusive. Common combinations:

| Combination | How It Works |
|-------------|--------------|
| **SCQA → Pyramid** | Use SCQA to frame the problem, then Pyramid to deliver the structured answer |
| **Three-Act + Triad** | Structure the story in three acts; ensure each act has data, narrative, and visuals |
| **AIDA + "So What?"** | Use AIDA for overall structure; apply "So What?" to each finding within the Interest and Desire stages |
| **Any framework + Triad** | The Triad is a completeness check that works inside any structural framework |

## Matching Framework to Deliverable Type

| Deliverable | Primary Framework | Why |
|-------------|-------------------|-----|
| Executive summary | Pyramid Principle | Executives want the answer first |
| Policy brief | SCQA | Policymakers need to understand the problem before the evidence |
| Stakeholder presentation | Three-Act or AIDA | Presentations benefit from narrative arc |
| Research report | "So What?" + Triad | Each finding needs implications; all three elements must be present |
| Media talking points | SCQA (compressed) | Journalists need the hook (complication) and the answer |
| Funding proposal | AIDA | The goal is commitment, not just comprehension |

## References and Further Reading

Dykes, B. (2019). *Effective Data Storytelling: How to Drive Change with Data, Narrative, and Visuals*. Wiley. https://www.effectivedatastorytelling.com/

Minto, B. (2010). *The Pyramid Principle: Logic in Writing and Thinking*. 3rd Edition. Pearson.

Nussbaumer Knaflic, C. (2015). *Storytelling with Data: A Data Visualization Guide for Business Professionals*. Wiley. https://www.storytellingwithdata.com/

Alan Alda Center for Communicating Science. https://www.aldacenter.org/

AAAS. "Communication Toolkit." https://www.aaas.org/resources/communication-toolkit
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall