Data Storytelling Slide Pack & Narrative Templates

Purpose

This slide pack and narrative template helps analysts and teams turn analysis into a short, persuasive presentation that prompts action. Use it to: connect evidence to a clear recommendation, surface key trade-offs and uncertainties, name ownership, and define measurable next steps so stakeholders can decide and move forward.

How to use this template

1. Start with the executive summary slide: state the decision you want and the recommended action in a single sentence.
2. Put the strongest supporting evidence up front. If a single chart or number tells the story, show it prominently.
3. Use the Alternatives and Trade-offs slide to show what you considered and why the recommendation is preferable.
4. Always close with ownership, next steps, success metrics, and a short summary of assumptions and uncertainty.
5. Keep the core deck short (6–10 slides). Put detailed methods, data tables, and technical notes in the appendix.

Suggested slide list (brief)

1. Title / Context — one-line topic, presenter, date, audience
2. Executive Summary — decision requested, recommended action, one-line rationale
3. Why it matters — clear goal, metric(s) affected, business impact
4. Key Evidence — 1–2 high-impact visuals and the essential numbers
5. Alternatives & Trade-offs — options considered and relative pros/cons
6. Recommendation & Rationale — what to do, why, and expected outcome
7. Impact Estimate & Assumptions — benefits, costs, timing, critical assumptions
8. Confidence & Risks — uncertainty, sensitivity, mitigation steps
9. Next Steps, Owner & Success Metrics — who, when, how success will be measured
10. Appendix / Methods — data sources, definitions, calculations, full charts

Slide-by-slide guidance (what to include and why)

Executive Summary

What to include: the decision you want stakeholders to make; the recommended action; one sentence explaining why (impact in a relevant metric). Keep it one or two lines. Treat this slide like an email subject line for the meeting.

Why it matters

Explain the goal and the metric(s) that will change if the recommendation is adopted. Tie to business outcomes (revenue, cost, safety, compliance, customer satisfaction) and show a simple baseline and target.

Key Evidence

Show 1–2 visuals that most directly support the recommendation. Use clear titles, concise captions that state the insight (not just the chart description), and callouts for the most important numbers.

Alternatives & Trade-offs

List plausible options, estimated impacts, and important trade-offs (cost, time, risk, customer impact). Use a short table or 3-4 bullets—don’t bury trade-offs in the appendix.

Recommendation & Rationale

State the recommended action in an imperative form (e.g., "Deploy X to Y pilot group for 90 days"). Explain why it was chosen and link to the key evidence slide(s).

Impact Estimate & Assumptions

Include numerical impact estimates (best, likely, worst) and list the assumptions that matter most. If appropriate, show a simple sensitivity table or range chart.

Confidence & Risks

Be explicit about confidence level and main risks. Offer mitigation steps for the top 2–3 risks so decision-makers see you’ve thought through plausible failures.

Next Steps, Owner & Success Metrics

End with a single slide that names who will do what by when, how success will be measured, and the first check-in date. Use a mini RACI-style table if useful (Owner, Support, Deadline).

Speaker notes: framing trade-offs & uncertainty

Use these short cues while presenting:

• "Here’s the decision we’re asking for and why it matters right now."
• "This chart shows the central signal we’re monitoring — the trend and the magnitude."
• "These were the main alternatives we tested and why they didn’t meet our goals as well as the recommendation."
• "Our impact estimate depends on assumption A and B; here’s how we’ll validate those early."
• "If you approve, the first deliverable and check-in will be X on this date; the owner will be Y."

Evidence quality & decision checklist

Before presenting, run the checklist and fix any "No" answers or explain them openly in the appendix:

• Is the primary metric clearly defined and measurable? (yes / no)
• Is the data source reliable and documented? (yes / no)
• Have key assumptions been stated and justified? (yes / no)
• Have we estimated benefits and costs with ranges or sensitivity? (yes / no)
• Is a single owner named for implementation and follow-up? (yes / no)
• Does the deck include a clear, specific ask (approve, pilot, invest, review)? (yes / no)

Visual guidance (quick rules)

• Prefer simple charts: line for trends, bar for comparisons, waterfall for contributions, scatter for correlations.
• Label axes, use meaningful ticks, and remove redundant gridlines.
• Highlight the one number or segment you want your audience to notice (color + annotation).
• Aim for 1 insight per visual; avoid multi-axis charts unless absolutely necessary and clearly explained.

Example opening script (30–45 seconds)

"We’re here to decide whether to proceed with [recommended action]. In one sentence: we recommend [action] because it would reduce [problem] by roughly [impact estimate], improving [metric]. The data we’ll show focuses on the signal that matters and the main trade-offs you should consider. If you approve, [owner] will start a [timeframe] pilot and we’ll measure success by [metric]."

Appendix suggestions

Include technical details that support reproducibility and deeper review, such as data definitions, query snippets, modeling approach, confidence intervals, and full-size charts.

Time allocation guidance

For a 15–25 minute meeting: 2 minutes to state the decision and recommendation, 8–12 minutes to present evidence and trade-offs, 3–6 minutes for next steps and Q&A. Reserve extra time for discussion if the decision requires cross-functional alignment.

Why this template helps

It flips the default ‘‘what happened’’ report into a ‘‘what should we do’’ decision packet by forcing a clear recommendation, ownership, measurable outcomes, and explicit uncertainty—so presentations become action drivers rather than status updates.

Save & adapt

Copy this template into your team’s collection and adapt the language, metrics, and appendix to your organization’s standards. Keep a version history so future presenters can reuse proven slides and update assumptions.