stakeholder-readoutlisted

# Stakeholder Readout ## When to use this skill Use whenever an analysis output needs to be communicated to a non-DS audience (PM, eng, exec, sales). Triggers: - "Write a readout for…" - "Summarize the findings" - "Make this stakeholder-friendly" - "Exec summary of…" - "Share this with the team" Pair with any analysis-producing skill (`ab-test-analysis`, `cohort-analysis`, `survival-analysis`, etc.). This skill is the **packaging layer**. ## Required inputs | Input | Why it matters | |---|---| | Question being answered | The decision this informs | | Audience | PM / Exec / Eng / Mixed — affects depth | | Key finding | The 1-2 sentence headline | | Evidence (data / charts) | Numbers backing the finding | | Confidence level | How sure are we? | | Recommended decision | What you'd do if it were your call | ## The readout structure Every readout has exactly five sections, in this order: 1. **TL;DR** — One sentence, one decision recommendation 2. **Context** — What question + why now 3. **Findings** — 2-5 key facts with evidence 4. **Decision** — What to do, by whom, by when 5. **Caveats & next steps** — What we don't know ## Workflow 1. **Write the TL;DR first.** If you can't summarize in one sentence, you don't understand it yet. The TL;DR must contain: - The answer to the question - The recommended action - Confidence indicator ("strong evidence" / "directional" / "preliminary") 2. **List 2-5 findings**, each with: - The fact (one sentence) - The data