Skip to content

DAAF-Contribution-Community/daaf / .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/audience-analysis.md

View on GitHub
# Audience Analysis

How to adapt your communication strategy based on who is reading. Every dimension of your deliverable — structure, vocabulary, detail level, uncertainty communication, visuals, and length — changes based on the audience.

The AAAS communication framework puts it simply: **Goal → Audience → Message.** Define your purpose, identify who can act on it, then craft language for that specific reader. Never write first and identify the audience second.

The example sentences, chart titles and numbers in this file are invented for illustration, including the reading-program and class-size scenario in the tone table (200 districts, $8M, 15 and 42 cents); they are not research findings.

## The Five Audience Types

### 1. Academic Researchers

Peers and reviewers who share your methodological vocabulary and expect full technical transparency.

| Dimension | Strategy |
|-----------|----------|
| **Structure** | Introduction → Literature → Methods → Results → Discussion → Conclusion. Follow disciplinary conventions. |
| **Vocabulary** | Full technical language appropriate. Define novel terms or terms used non-standardly. |
| **Detail level** | Comprehensive. Full methodology, robustness checks, sensitivity analyses, all coefficient tables. |
| **Uncertainty** | Report exact p-values, confidence intervals, effect sizes. Use field-standard notation. Discuss threats to identification explicitly. |
| **Caveats** | Exhaustive. Every limitation, every assumption, every boundary condition. Reviewers will find what you omit. |
| **Visuals** | Dense, information-rich. Coefficient plots, regression tables, diagnostic plots. Assume chart literacy. |
| **Length** | As needed — 20-40 pages typical for working papers. Appendices for supplementary material. |
| **Purpose** | Demonstrate rigor, advance knowledge, invite critique, establish contribution to literature. |

**What makes academic communication distinct:** Comprehensiveness is valued over conciseness. The reader is assessing your *methodology* as much as your *findings*. Every analytical choice needs justification.

---

### 2. Policymakers and Legislative Staff

Decision makers working under time constraints who need evidence translated into actionable implications. They often have staff who brief them, so your materials may be read by intermediaries with varying technical backgrounds.

| Dimension | Strategy |
|-----------|----------|
| **Structure** | Bottom-line first → Key findings (3 max) → Evidence summary → Policy implications → Caveats. Inverted pyramid: the first paragraph must stand alone. |
| **Vocabulary** | Plain language. Replace statistical jargon with accessible equivalents (see `plain-language.md`). Define any technical term you must use. |
| **Detail level** | Selective. Present the 3-5 findings most relevant to the policy question. Methodology in a brief appendix or sidebar, never the main text. |
| **Uncertainty** | Qualitative hedging: "the evidence strongly suggests," "we found consistent patterns across multiple measures." Avoid p-values and confidence intervals in main text. Include a brief "strength of evidence" summary. |
| **Caveats** | The 2-3 most important limitations only — specifically those "too important to exclude" (IES). Over-caveating obscures the finding and undermines confidence. |
| **Visuals** | Clean, simple charts with declarative titles ("Rural Schools Lost Teachers Fastest"). One message per chart. No regression tables — use coefficient plots or simplified comparison charts. |
| **Length** | 2-4 pages for briefs. 1 page for executive summaries. Assume only the first page will be read. |
| **Purpose** | Inform a decision. Translate evidence into implications without prescribing specific policy choices. |

**What makes policy communication distinct:** Policymakers are buying *decision-relevant evidence*, not evaluating your methodology. They need to know: What did you find? How confident should I be? What does it mean for my decision? The IES blog post's sixth strategy is "Conclude by summarizing not extrapolating" — present what the evidence shows without overstepping into prescription.

**Preparing for policymaker engagement (AAAS):**
- Understand where in the policy cycle your evidence is relevant (AAAS: review evidence, identify and appraise options, assess uncertainties and risks, choose and implement an option, monitor progress)
- Define your "ask" before the meeting — what action are you requesting?
- Be prepared for conversations of only a few minutes
- Identify overlapping interests between your work and their agenda

---

### 3. Executives and Board Members

Senior leaders making resource allocation decisions. They want strategic implications, not analytical details. Their question is always: "What should we do differently?"

| Dimension | Strategy |
|-----------|----------|
| **Structure** | Recommendation → Supporting evidence (3 bullets max) → Risk assessment → Next steps. Every section answers "so what?" |
| **Vocabulary** | Business language. Translate statistical findings into organizational impact. "Our analysis shows a 12-point gap" → "Students in our lowest-performing schools are a full grade level behind." |
| **Detail level** | Minimal. The executive summary IS the deliverable. Technical details available on request, never in the main document. |
| **Uncertainty** | Directional confidence: "We are highly confident that..." / "The evidence is suggestive but not conclusive..." / "We don't yet have enough data to determine..." Frame uncertainty as risk to the decision, not as statistical properties. |
| **Caveats** | Only caveats that affect the recommendation. Frame as "What could change this picture" rather than methodological limitations. |
| **Visuals** | 1-2 high-impact charts maximum. Simple bar charts or line charts with bold declarative titles. No chart should require more than 10 seconds to interpret. |
| **Length** | 1 page, ideally 1 screen. If they want more, they will ask. |
| **Purpose** | Drive a decision. Make the path from evidence to action self-evident. |

**What makes executive communication distinct:** Executives optimize for *decision speed*, not comprehension depth. They will not read beyond the first page unless you have earned their interest. The Pyramid Principle (see `narrative-frameworks.md`) was designed for this audience: lead with the answer, then provide supporting logic only as deep as needed.

---

### 4. General Public and Community Members

Diverse audiences with varying educational backgrounds, lived experiences, and reasons for engaging with your findings. Includes community stakeholders, parents, local advocacy groups, and interested citizens.

| Dimension | Strategy |
|-----------|----------|
| **Structure** | Headline finding → "Why this matters to you" → Supporting evidence as narrative → What happens next. Mirror news article structure. |
| **Vocabulary** | Everyday language, 9th-11th grade reading level (see `plain-language.md`). Zero jargon. Every technical concept needs an analogy or concrete example. |
| **Detail level** | Minimal. 1-3 key findings maximum. Concrete, specific examples over abstract statistics. "1 in 5 students" is more impactful than "20% of the student population." |
| **Uncertainty** | Everyday probability language: "We're quite confident," "The evidence points strongly toward," "We can't be sure yet, but the pattern is clear." Never use statistical terminology. |
| **Caveats** | 1 caveat maximum, stated as a plain-language qualification: "This study looked at public schools in three states — the pattern may differ elsewhere." |
| **Visuals** | Simple bar charts, waffle charts ("7 out of 10"), icon arrays. Infographic style is appropriate. Declarative titles are mandatory. Every chart needs a one-sentence plain-language takeaway. |
| **Length** | Under 1 page for written materials. 3-5 minutes for presentations. Brevity is kindness. |
| **Purpose** | Inform, build trust, create shared understanding. Respect the audience's intelligence while meeting them where they are. |

**What makes public communication distinct:** The public audience is the most heterogeneous — they have no shared technical vocabulary and no obligation to keep reading. You must earn their attention with immediate relevance and maintain it with clarity. NIH's *Clear & Simple* guide notes that people with average or good reading skills also appreciate messages conveyed simply and clearly — simplicity is a feature, not a concession.

**Critical framing consideration:** People may see themselves in your data. If your findings are about communities, schools, or demographic groups, readers may be members of those groups. Communicate with empathy and respect. See `accessibility-equity.md` for equity-aware framing guidance.

---

### 5. Journalists and Media

Intermediaries who translate your work for their own audiences. Journalists work to tight deadlines, write in their own style, and aim to inform rather than educate. You cannot control the final product — you can only provide the best raw material.

| Dimension | Strategy |
|-----------|----------|
| **Structure** | Two questions journalists always ask: (1) What is new? (2) Why should readers care? Prepare clear answers to both before any interaction. |
| **Vocabulary** | Conversational. Prepare sound bites — short, quotable sentences that convey the key finding accurately. Practice saying findings out loud. |
| **Detail level** | Prepare three tiers: (1) the headline in one sentence, (2) supporting context in 2-3 sentences, (3) full methodology available on request. The journalist chooses their depth. |
| **Uncertainty** | Pre-prepare hedged quotable statements: "Our study found strong evidence that..." rather than "p < 0.001 for the primary coefficient." Provide analogies for uncertainty: "This is about as confident as we get in this field." |
| **Caveats** | Proactively state the 1-2 biggest limitations as quotable sentences. If you don't provide the caveat, it likely won't appear. Better to frame your own limitation than have someone else frame it for you. |
| **Visuals** | Provide publication-ready charts with clear titles and source notes. Offer the data behind the chart. Simple, reproducible graphics travel further than complex ones. |
| **Length** | For interviews: prepare for 15-30 minutes but assume only 1-2 sentences will be quoted. For press releases: 1 page. For backgrounders: 2-3 pages. |
| **Purpose** | Equip the journalist to tell an accurate story. Build a relationship for future coverage. |

**What makes media communication distinct:** You are providing raw material, not a finished product. Journalists will select, condense, and reframe. Your job is to make the accurate version of the story the easiest one to tell. The AAAS recommends getting to know local journalists and being a resource for their questions, and working with your institution's public information officers, who act as liaisons between scientists and journalists and can help prepare interviews and core messages.

**Pre-interview preparation (AAAS checklist):**
- Who is the journalist's audience and what do they value?
- What is your three-point core message?
- Why should their specific audience care?
- Which difficult or controversial questions might come up, and how will you answer them?

---

## Tone and Register by Audience

The same content changes not just in vocabulary and structure but in *tone* — the emotional register that signals respect, competence, and appropriate relationship with the reader.

| Audience | Tone | Register | Example Opening |
|----------|------|----------|-----------------|
| **Academic** | Measured, precise, neutral | Formal-analytical | "This study examines the relationship between instructional investment type and reading proficiency gains across 200 districts." |
| **Policy** | Authoritative, balanced, evidence-grounded | Formal-professional | "New evidence on reading improvement strategies has direct implications for how states allocate instructional funding." |
| **Executive** | Confident, direct, action-oriented | Professional-concise | "We recommend shifting $8M from class-size reduction to literacy programs. Here's why." |
| **Public** | Warm, accessible, respectful | Conversational-clear | "A new study looked at what actually helps kids learn to read better — and the answer might surprise you." |
| **Media** | Engaging, concrete, quotable | Conversational-vivid | "For every dollar spent on smaller classes, schools got 15 cents of reading improvement. Structured reading programs returned 42 cents." |

**The key rule:** Your tone should signal respect for the audience's intelligence while meeting them at their vocabulary level. A warm tone for the public is not condescending; a formal tone for academics is not cold. Match the register to the relationship, not just the content.

## What Changes Across Audience Levels

This comparison table highlights the dimensions that shift most dramatically across audiences:

| Dimension | Academic | Policy | Executive | Public | Media |
|-----------|----------|--------|-----------|--------|-------|
| **Opens with** | Gap in literature | Bottom-line finding | Recommendation | "Why this matters to you" | What's new |
| **Methodology** | Comprehensive | Brief appendix | Absent | Absent | Available on request |
| **Jargon tolerance** | High | Low | Very low | None | Conversational |
| **Uncertainty style** | Quantitative (CI, p) | Qualitative hedging | Risk framing | Everyday probability | Quotable hedges |
| **Caveat depth** | Exhaustive | Top 2-3 | Decision-relevant only | 1 max | Proactive framing |
| **Visual complexity** | High (dense) | Moderate (clean) | Minimal (bold) | Simple (intuitive) | Reproducible |
| **Tone** | Measured, neutral | Authoritative, balanced | Confident, direct | Warm, accessible | Engaging, quotable |
| **Reading commitment** | 30+ minutes | 5-10 minutes | 60 seconds | 2-3 minutes | Varies by format |
| **Success metric** | Advances knowledge | Informs decision | Drives action | Builds understanding | Accurate coverage |

## Audience Assessment Checklist

Before drafting any deliverable, answer these questions:

- [ ] **Who is the primary audience?** (Name the specific type, not "stakeholders")
- [ ] **What is their existing knowledge level?** (Can they interpret a regression table? A bar chart? A percentage?)
- [ ] **What decision or action does this communication support?** (If none, reconsider whether the deliverable is needed)
- [ ] **How much time will they spend with this?** (This determines your length and structure)
- [ ] **What is their vocabulary?** (Use their words, not yours)
- [ ] **What do they already believe about this topic?** (Align your framing with or explicitly address their priors)
- [ ] **Will they see themselves in this data?** (If yes, review equity framing — see `accessibility-equity.md`)
- [ ] **Is there a secondary audience?** (A policy brief may be read by both the policymaker and their staff, who have different knowledge levels)
- [ ] **What is the delivery format?** (Print, screen, presentation, conversation — each has different constraints)
- [ ] **What is the single most important takeaway?** (If you can't state it in one sentence, you're not ready to write)

## Mixed Audiences

When your audience is heterogeneous (e.g., a presentation to a room with both technical and non-technical attendees), layer your communication:

1. **Lead at the lowest common denominator** — state findings in plain language first
2. **Provide depth on demand** — "For those interested in the methodology..." or appendices for technical readers
3. **Use the "newspaper test"** — would the headline version of your finding be accurate? Start there, then add nuance
4. **Label technical content explicitly** — "Technical note:" or "For researchers:" signals that non-technical readers can skip ahead

## References and Further Reading

AAAS. "Communication Toolkit." https://www.aaas.org/resources/communication-toolkit

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

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

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

NIH. "Clear & Simple." https://www.nih.gov/institutes-nih/nih-office-director/office-communications-public-liaison/clear-communication/clear-simple (archived 2024-01-11)
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