DAAF-Contribution-Community/daaf / .claude/skills/science-communication
science-communication
VerifiedTranslating 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
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.0 KB |
| references/accessibility-equity.md | markdown | 19.3 KB |
| references/audience-analysis.md | markdown | 16.5 KB |
| references/communication-review.md | markdown | 16.8 KB |
| references/deliverable-templates.md | markdown | 19.8 KB |
| references/narrative-frameworks.md | markdown | 19.4 KB |
| references/plain-language.md | markdown | 30.3 KB |
references/deliverable-templates.md
View on GitHub# Deliverable Templates
Structural outlines, rules, and example skeletons for four core communication deliverable types. Each template is designed for a specific audience and purpose — choose based on who will read it and what decision it supports.
For audience-specific strategy, see `audience-analysis.md`. For narrative structure choices, see `narrative-frameworks.md`.
**Note on examples:** Every example in this file is invented. The Example Skeleton blocks share one scenario (structured literacy programs compared with class-size reduction for improving reading), and the sample titles and quoted sentences elsewhere in the file are made up too. Their numbers, districts, dates and findings are illustrative, not research findings.
## 1. Executive Summary
**Audience:** Executives, board members, senior decision makers
**Purpose:** Deliver the bottom line and its implications in the shortest possible format
**Framework:** Pyramid Principle (answer first, then supporting logic)
### Structural Outline
| Section | Max Length | Content |
|---------|-----------|---------|
| **Bottom line** | 1-2 sentences | The single most important finding or recommendation. This is the answer. |
| **Key findings** | 3-5 bullets | Supporting evidence, one bullet per finding. Each bullet should stand alone. |
| **Methodology note** | 1-2 sentences | What data, what time period, what approach — in plain language. No jargon. |
| **Implications** | 2-3 bullets | What this means for the organization. Translate findings into strategic impact. |
| **Caveats** | 1-2 sentences | Only limitations that could change the recommendation. Frame as "what could change this picture." |
| **Recommended next steps** | 2-3 bullets | Specific, actionable items with owners if possible. |
### Rules
1. **Maximum 10% of full document length.** A 20-page report gets a 2-page executive summary. A 5-page brief gets a half-page summary.
2. **Self-contained.** The reader should never need to consult the full report to understand the executive summary. Every claim must be interpretable without additional context.
3. **No new information.** Everything in the executive summary must appear in the full document. The summary distills — it does not introduce.
4. **One page is ideal.** If it goes to two pages, it's not executive enough. Cut ruthlessly.
5. **Declarative titles on any embedded charts.** "Rural Districts Lost Teachers Fastest" not "Teacher Attrition by District Type."
6. **No methodology in the body.** The methodology note is a courtesy sentence, not a methods section. "We analyzed enrollment data for 13,000 districts over 8 years" is sufficient.
### Example Skeleton
> **Bottom line:** Early literacy interventions should replace class-size reduction as the district's primary reading improvement strategy, based on evidence showing 2-3x larger effects at 40% lower cost per student.
>
> **Key findings:**
> - Schools piloting structured literacy programs improved reading proficiency by 14 percentage points; schools with class-size reduction improved by 5 points
> - Cost per student served is $1,200 for literacy programs vs. $2,000 for class-size reduction
> - Effects are largest for students who entered below grade level — the highest-need population benefits most
>
> **Based on:** Analysis of 200 district reading programs (2019-2025), controlling for student demographics, baseline performance, and prior funding levels.
>
> **Implications:**
> - Current $14M class-size investment is producing below-benchmark returns
> - Redirecting $8M to literacy programs could serve 2x more students at higher effectiveness
> - Implementation timeline is 6-12 months vs. 2-3 years for further class-size changes
>
> **Caveat:** These findings are based primarily on elementary schools; middle school effects are less certain.
>
> **Next steps:**
> - Approve $2M pilot in 6 schools for 2026-27 (Board action needed by April)
> - Commission independent evaluation design by June
> - Report interim results to the Board in January 2027
---
## 2. Policy Brief
**Audience:** Policymakers, legislative staff, agency officials
**Purpose:** Inform a policy decision with evidence without prescribing a specific policy choice
**Framework:** SCQA (establish the problem, then present the evidence)
### Structural Outline
| Section | Max Length | Content |
|---------|-----------|---------|
| **Title** | 1 line | Descriptive but engaging. States the topic and finding direction, not the full conclusion. |
| **Summary box** | 3-5 bullets | Key takeaways in plain language. This is what gets read if nothing else does. |
| **Context** | 1-2 paragraphs | Why this issue matters now. What policy question is at stake. What the current landscape looks like. (SCQA: Situation + Complication) |
| **What the evidence shows** | 2-4 paragraphs + 1-2 figures | Core findings, each linked to a policy-relevant implication. Lead each paragraph with a numbers-free headline sentence (IES Strategy 2). |
| **Policy alternatives** | 2-4 paragraphs | Present options, not a single recommendation. For each alternative: what it does, what evidence supports it, what tradeoffs it involves. |
| **What we don't know** | 1 paragraph | Key limitations framed as open questions, not methodological confessions. "The evidence does not yet tell us whether..." |
| **Sources and methodology** | Brief appendix | Data sources, time period, approach. Available for staff who want to assess credibility. |
### Rules
1. **2-4 pages maximum.** Policy briefs that exceed 4 pages lose their audience. If you need more space, write a report and attach a 1-page summary.
2. **No jargon in the body.** Every technical term must be translated. See `plain-language.md`.
3. **Present alternatives, not prescriptions.** The researcher's role is to present evidence and illuminate tradeoffs. The policymaker's role is to decide. "Based on our analysis, three approaches merit consideration..." not "We recommend..."
4. **Lead each paragraph with the finding in plain language.** Follow IES Strategy 2: the first sentence of each evidence paragraph states the insight without numbers. Numbers come in the supporting sentences.
5. **Include only the most essential caveats** — those "too important to exclude" (IES Strategy 4). Over-caveating undermines confidence without serving the reader.
6. **Every figure must be self-interpreting.** Declarative title, clear labels, source note. A policymaker should understand the chart without reading surrounding text.
7. **Conclude by summarizing, not extrapolating.** Per IES Strategy 6: present what the evidence shows and its implications, not explicit policy recommendations.
### Example Skeleton
> **Title:** Early Literacy Programs Outperform Class-Size Reduction for Reading Improvement
>
> **Key Takeaways:**
> - Structured literacy programs improved reading scores 2-3 times more than class-size reduction
> - Literacy programs cost 40% less per student served
> - Benefits were largest for students entering below grade level
> - Evidence is based on 200 districts over 6 years; results were consistent across diverse contexts
>
> **Context:** Since 2005, our state has invested heavily in reducing class sizes as a strategy for improving student outcomes. [Situation.] However, our analysis suggests that *how* instructional time is used may matter more than *how many* students share the classroom. [Complication.]
>
> **What the evidence shows:**
> Schools using structured literacy programs saw substantially larger reading gains than those relying on class-size reduction alone. [Headline — no numbers.] Specifically, literacy program schools improved proficiency rates by 14 percentage points compared to 5 points for class-size reduction schools, after accounting for student demographics and baseline performance. [Supporting evidence.]
>
> The benefits were not uniform across all students. [Headline.] Students who entered below grade level showed the largest gains — 18 percentage points in literacy programs versus 4 points with smaller classes. [Supporting evidence.]
>
> **Policy alternatives:**
> - *Option A: Full reallocation* — redirect class-size funds to literacy programs...
> - *Option B: Phased transition* — pilot literacy programs alongside existing class-size commitments...
> - *Option C: Targeted deployment* — maintain class-size investments in early grades, redirect in upper elementary...
>
> **What we don't know:** The evidence does not yet tell us whether these effects persist beyond elementary school, nor whether the same programs work equally well in rural and urban settings.
---
## 3. Stakeholder Presentation
**Audience:** Mixed groups (board members, managers, practitioners, community members)
**Purpose:** Build shared understanding and move toward a decision or next steps
**Framework:** Three-Act Data Story or AIDA, depending on whether the goal is understanding or buy-in
### Structural Outline
| Section | Slides | Content |
|---------|--------|---------|
| **Opening hook** | 1 | A striking finding, a compelling question, or a human story that makes the topic immediate. Earn attention in the first 30 seconds. |
| **Context** | 1-2 | What is the situation? Why does this matter now? What question are we answering? |
| **Key findings** | 3-5 | One finding per slide. Declarative title at the top. One supporting chart or visual. 2-3 bullet points maximum. |
| **What it means** | 1-2 | Translate findings into implications for this specific audience. "So what?" for each finding. |
| **Recommendations / options** | 1-2 | What should happen next? Be specific. If the audience needs to decide, frame the decision clearly. |
| **Discussion** | 1 | Open with a specific question, not "any questions?" Try: "Given these findings, what concerns do you have about Option B?" |
### Rules
1. **One message per slide.** If you need two charts, use two slides.
2. **Slide titles are declarative sentences** that state the finding. "Rural Districts Lost Teachers Fastest" — not "Teacher Attrition Data." The title should tell the story even if the audience doesn't look at the chart.
3. **Maximum 3-5 bullets per slide, maximum 6-8 words per bullet.** Slides are visual aids, not documents. If you're reading your slides, you've written a document.
4. **Presenter notes, not slide text.** The detail goes in your spoken remarks, not on the slide. The audience should be listening to you, not reading ahead of you.
5. **Design for the back row.** Minimum 24pt for body text, 32pt for titles. If they can't read it from the back of the room, cut it.
6. **Consistent visual language.** Same color means the same thing across all slides. Same chart style throughout. See data-scientist visualization references for chart construction standards.
7. **Build in pauses for questions.** After key findings slides, pause. "Does this match your experience?" invites engagement and surfaces misunderstanding early.
8. **End with a specific ask or clear next step.** Never end with "Questions?" without first stating what you need from the audience.
### Example Skeleton
> **Slide 1 (Hook):** "Our highest-need students are falling further behind — but three schools found a way to reverse the trend." [Photo or simple chart showing the gap]
>
> **Slide 2 (Context):** The district invested $14M in class-size reduction since 2019. Reading scores have remained flat. [Simple trend line]
>
> **Slide 3 (Finding 1):** "Literacy programs produced 3x the reading gains of class-size reduction." [Paired bar chart, two bars]
>
> **Slide 4 (Finding 2):** "The biggest gains went to students who needed them most." [Chart showing effect by baseline level]
>
> **Slide 5 (Finding 3):** "Literacy programs cost 40% less per student." [Cost comparison chart]
>
> **Slide 6 (What it means):** Redirecting resources could serve twice as many students at higher effectiveness.
>
> **Slide 7 (Recommendation):** Proposed pilot: 6 schools, $2M, starting fall 2026. Board approval needed by April.
>
> **Slide 8 (Discussion):** "What would you need to see from the pilot to support district-wide expansion?"
---
## 4. Media Talking Points
**Audience:** Journalists and through them, the general public
**Purpose:** Equip journalists to tell an accurate story about your findings
**Framework:** SCQA (compressed) — the hook and the answer
### Structural Outline
| Section | Content |
|---------|---------|
| **Headline finding** | One sentence that answers: "What is new?" Make it quotable. |
| **Why it matters** | One sentence that answers: "Why should readers care?" Connect to something the audience experiences. |
| **Supporting context** | 2-3 sentences with the most compelling supporting data. Concrete numbers, specific comparisons. |
| **Prepared analogies** | 1-2 analogies or comparisons that make abstract findings tangible. "That's the equivalent of..." |
| **Proactive caveat** | 1 sentence stating the most important limitation, framed constructively. Better to frame your own limitation than have someone else frame it. |
| **Quotable hedged statement** | A pre-prepared sentence you would be comfortable seeing in print, with appropriate uncertainty. |
| **Background (if asked)** | 2-3 sentences on methodology, available for journalists who want to assess credibility. |
### Rules
1. **Prepare for 1-2 quoted sentences.** Even from a 30-minute interview, most stories use 1-2 direct quotes. Make those quotes count. Practice saying them out loud until they're natural.
2. **No jargon.** Not even "statistically significant." Journalists will either skip the term or misdefine it.
3. **Provide the headline.** If you don't give the journalist a clear headline, they'll write their own — and it may not be the most accurate version of your finding.
4. **Prepare three tiers of depth.** (1) The headline in one sentence. (2) Supporting context in 2-3 sentences. (3) Full methodology on request. Let the journalist choose their depth.
5. **Proactively state limitations.** If you don't provide the caveat, it likely won't appear. But frame it constructively: "This study focused on elementary schools — we're now extending to middle schools" rather than "A limitation of this study is..."
6. **Analogies travel further than numbers.** A plain comparison ("roughly the gap between fourth and fifth grade") is more quotable than an effect in standard deviations. Use such a conversion only when your own data or a cited benchmark supports it for the grade and test involved.
7. **Never say "no comment."** If you can't answer, explain why and offer to follow up.
### Example Skeleton
> **Headline finding:** "Schools that switched from smaller classes to structured reading programs saw three times the improvement in student reading scores."
>
> **Why it matters:** "Millions of dollars are being spent on a strategy that produces smaller results than a cheaper alternative — and the students who need the most help are benefiting the least from the current approach."
>
> **Supporting context:** "We studied 200 school districts over six years. Districts that adopted early literacy programs saw reading proficiency rise by 14 percentage points. Districts that focused on reducing class sizes saw only a 5-point improvement. The difference was even larger for students who started behind."
>
> **Prepared analogy:** "The gap between the two approaches is like the difference between walking and driving — both get you there, but one is dramatically faster, and the students with the longest journey benefit the most from the faster route."
>
> **Proactive caveat:** "This evidence is strongest for elementary schools. We're now investigating whether the same pattern holds in middle schools."
>
> **Quotable hedged statement:** "Our analysis provides strong evidence that how instructional time is used matters more than class size for reading improvement — and that the students most in need benefit the most from structured literacy approaches."
---
## How to Distill: Turning Long Reports into Short Deliverables
One of the most common tasks: "I have a 15-page report and need a 1-page executive summary." The deliverable templates above describe the *output* format. This section describes the *process* of distillation.
### The Distillation Process
1. **Read the report's conclusion first.** The bottom line is usually buried at the end. Extract it — this becomes the opening sentence of your short deliverable.
2. **Identify the 3 most important findings.** Not the 3 most interesting, not the 3 you worked hardest on — the 3 that most directly answer the original research question or inform the audience's decision. If you can't choose 3, ask: "If the reader remembers only one finding, which one?"
3. **For each finding, extract: the claim, the evidence, and the implication.** Strip away methodological detail, robustness checks, and supporting analysis. These belong in the full report, not the summary.
4. **Translate vocabulary.** Run every sentence through the audience-appropriate vocabulary filter (see `plain-language.md`). Replace jargon. Shorten sentences. Use active voice.
5. **Cut methodology to one sentence.** "We analyzed enrollment data from 13,000 districts over 8 years" is usually sufficient. If more is needed, it goes in a brief appendix or "methodology note" box.
6. **Apply the caveat filter.** Include only caveats that could change the reader's interpretation of the bottom line. "More research is needed" is never a caveat worth including. "These results only apply to elementary schools" might be.
7. **Check: does the short version faithfully represent the long version?** The distilled deliverable must not say something the full report does not support. Simplification is acceptable; misrepresentation is not.
### What to Cut vs. What to Keep
| Cut | Keep |
|-----|------|
| Literature review and background | Bottom-line finding |
| Methodological detail | One-sentence methodology note |
| Robustness checks and sensitivity analyses | Key findings (3 max) |
| All but the most important caveats | Decision-relevant limitations |
| Data description and variable definitions | Implications and next steps |
| Tables with many rows/columns | One or two high-impact charts |
| "As expected" findings | Surprising or counterintuitive findings |
### Managing Nuance Loss
Distillation inevitably loses nuance. Manage this honestly:
- **Acknowledge what is lost.** "This summary covers the headline findings. For methodology, robustness checks, and subgroup analyses, see the full report."
- **Don't overstate in the short version.** If the full report says "the evidence suggests," the summary should not say "the evidence proves."
- **Provide a path to depth.** Always link or reference the full report for readers who want more.
## Cross-Deliverable Consistency
When a single analysis produces multiple deliverable types (e.g., a full report, an executive summary, a policy brief, and a presentation), maintain consistency:
- [ ] The same finding is stated the same way across all deliverables (adapted for audience, not contradicted)
- [ ] Numbers are identical everywhere they appear
- [ ] Charts use the same color coding and style across formats
- [ ] Caveats included in shorter deliverables are a subset of those in longer ones (never introduce new caveats in the summary)
- [ ] The "bottom line" is consistent: if the report says A, the executive summary cannot say B
## References and Further Reading
Miller, L. C., & Piver-Renna, J. (2022, October 27). "Six Strategies for Effectively Communicating Research Findings to Decision Makers." Institute of Education Sciences. https://ies.ed.gov/learn/blog/six-strategies-effectively-communicating-research-findings-decision-makers
Minto, B. (2009). *The Pyramid Principle: Logic in Writing and Thinking* (3rd ed.). Financial Times Prentice Hall.
Nussbaumer Knaflic, C. (2015). *Storytelling with Data: A Data Visualization Guide for Business Professionals*. Wiley.
Schwabish, J. (2021). *Better Data Visualizations: A Guide for Scholars, Researchers, and Wonks*. Columbia University Press.
AAAS. "Communication Toolkit." https://www.aaas.org/resources/communication-toolkit
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |