Browse a larger categorized library built for this specific writing intent. Search the collection, filter by situation, and compare how the underlying pattern changes with purpose and context.
Strong data storytelling starts with the decision or question, selects only the evidence needed to answer it, gives readers scale and comparison, distinguishes observation from explanation, and ends with a consequence, recommendation, or next question that is proportionate to the evidence.
Start with the audience question or decision, not with every metric available.
State the main finding in plain language and identify the comparison, time period, denominator, or baseline that gives it meaning.
Use a chart, table, or small set of numbers only when it makes the pattern easier to verify.
Explain why the finding matters while separating observed association from inferred cause.
Name uncertainty, missing data, exceptions, or competing explanations when they affect the decision.
Close with the implication, recommendation, or next question the evidence actually supports.
Worked format lab
See complete reasoning, not just isolated lines
Use these fuller examples to see what changes between a recognizable pattern and a finished piece of writing. The examples are original or explicitly illustrative, so they demonstrate structure without inventing real-world evidence.
Worked example 1Average hides the tail
Illustrative service data
Headline: Typical cases are faster, but difficult cases are not.
Evidence: Median processing time fell from 18 to 12 minutes, while the 95th percentile remained near 61 minutes.
Interpretation: The workflow improved the common case without fixing the slowest cases.
Decision: Investigate the small set of cases driving the tail before claiming the whole process is faster.
Why it works: The story uses two statistics that change the interpretation rather than celebrating one favorable average.
Worked example 2Traffic is not conversion
Illustrative campaign data
Headline: The new creative earns more clicks but not more purchases.
Evidence: Click-through rate rose from 1.8% to 2.6%; conversion after the click remained about 3.1%.
Boundary: The data does not show whether the issue is audience quality, message match, or landing-page friction.
Next step: Test message-to-page consistency before scaling spend.
Why it works: Observation, uncertainty, and action are separated.
Prompt → finished structure
See the decisions between the assignment and the final form
These transformations make the hidden planning step visible so the template does not become a fill-in-the-blanks substitute for judgment.
Transformation 1Dashboard → decision story
Starting material: Source contains 18 KPIs and four charts.
Decisions Start from the decision, identify the two or three metrics that can change it, state the main finding, keep the relevant counter-signal, and move secondary diagnostics to supporting material.
Result: A short evidence narrative rather than a dashboard tour.
Transformation 2Trend → bounded interpretation
Starting material: Metric rises after a product change.
Decisions Describe the timing and scale first; check segments, denominator, seasonality, and simultaneous changes; label causal explanation as a hypothesis unless the design supports it.
Result: A persuasive but defensible data story.
Depth by level
Increase the reasoning, not just the word count
Level
What changes
Quality test
Basic explanation
State one pattern, give scale or comparison, and explain why it matters.
The reader can verify the claim from the numbers shown.
Decision narrative
Organize evidence around a decision, include a relevant exception or guardrail, and end with an action or question.
The story does not hide a metric that could reverse the interpretation.
Advanced analysis
Calibrate causal language, uncertainty, segmentation, and competing explanations; make the evidentiary boundary visible.
Narrative clarity does not exceed analytical support.
Reusable frameworks
Start from the decisions the format requires
Framework 1
Observation → function
1. What can the viewpoint actually perceive?
2. Which 1–2 details matter now?
3. What do those details change in image, pace, relationship, or action?
4. What interpretation remains uncertain?
Illustrative retention story: Week-one completion rose from 62% to 74% after the onboarding flow changed, while traffic mix remained similar. The strongest next question is whether the improvement persists across later cohorts before the team treats the redesign as the cause.
2
Editor picks
Illustrative service story: Support contacts fell overall, but billing contacts increased. The useful story is not “support improved”; it is that product-help demand declined while one billing problem became more visible and now deserves investigation.
3
Editor picks
Illustrative operations story: Median processing time improved, but the 95th percentile did not. For most cases the workflow is faster, yet difficult cases remain slow; the next improvement should target that tail rather than average speed.
4
Editor picks
Illustrative survey story: Satisfaction is higher among repeat users than new users. That pattern can guide onboarding research, but the survey alone does not show whether experience caused the difference.
5
Editor picks
Illustrative budget story: Spend is 6% under plan because two hires started later than expected, not because operating efficiency improved. The narrative separates timing variance from durable savings.
6
Editor picks
Illustrative campaign story: Click-through rate increased while conversion remained flat. The creative may be attracting attention without improving purchase intent, so the next test should examine message-to-landing-page fit.
7
Editor picks
Illustrative reliability story: Incident count declined, but total downtime increased because one event lasted much longer. Counting incidents alone would hide the customer impact.
8
Editor picks
Illustrative education story: Assignment completion improved most among students who used the new checklist, but participation was voluntary. The result supports further testing, not a claim that the checklist caused the improvement.
9
Support
Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged. Story: Typical cases improved; the tail still needs a separate response.
10
Support
Headline: Typical cases improved; the tail still needs a separate response. Evidence: Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged.
11
Support
Decision story — Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged. Implication: Typical cases improved; the tail still needs a separate response. Keep the causal boundary explicit.
12
Support
Chart narration — Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged. Do not hide the counter-signal: Typical cases improved; the tail still needs a separate response.
13
Support
Executive version — Typical cases improved; the tail still needs a separate response. Supporting evidence: Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged.
14
Support
Reader-question version — What should change next? Typical cases improved; the tail still needs a separate response. Evidence to keep visible: Median resolution time fell from 22 to 16 minutes, but the oldest cases remained unchanged.
15
Onboarding
Setup completion rose from 61% to 73%, while refund rate stayed within the prior range. Story: The change is promising, but later cohorts should confirm persistence.
16
Onboarding
Headline: The change is promising, but later cohorts should confirm persistence. Evidence: Setup completion rose from 61% to 73%, while refund rate stayed within the prior range.
17
Onboarding
Decision story — Setup completion rose from 61% to 73%, while refund rate stayed within the prior range. Implication: The change is promising, but later cohorts should confirm persistence. Keep the causal boundary explicit.
18
Onboarding
Chart narration — Setup completion rose from 61% to 73%, while refund rate stayed within the prior range. Do not hide the counter-signal: The change is promising, but later cohorts should confirm persistence.
19
Onboarding
Executive version — The change is promising, but later cohorts should confirm persistence. Supporting evidence: Setup completion rose from 61% to 73%, while refund rate stayed within the prior range.
20
Onboarding
Reader-question version — What should change next? The change is promising, but later cohorts should confirm persistence. Evidence to keep visible: Setup completion rose from 61% to 73%, while refund rate stayed within the prior range.
21
Campaign
Click-through rose from 1.7% to 2.4%, while conversion remained flat. Story: The creative earns attention without yet improving purchase behavior.
22
Campaign
Headline: The creative earns attention without yet improving purchase behavior. Evidence: Click-through rose from 1.7% to 2.4%, while conversion remained flat.
23
Campaign
Decision story — Click-through rose from 1.7% to 2.4%, while conversion remained flat. Implication: The creative earns attention without yet improving purchase behavior. Keep the causal boundary explicit.
24
Campaign
Chart narration — Click-through rose from 1.7% to 2.4%, while conversion remained flat. Do not hide the counter-signal: The creative earns attention without yet improving purchase behavior.
25
Campaign
Executive version — The creative earns attention without yet improving purchase behavior. Supporting evidence: Click-through rose from 1.7% to 2.4%, while conversion remained flat.
26
Campaign
Reader-question version — What should change next? The creative earns attention without yet improving purchase behavior. Evidence to keep visible: Click-through rose from 1.7% to 2.4%, while conversion remained flat.
27
Budget
Spend is 5% below plan because two hires started late. Story: The variance is timing, not proven efficiency.
28
Budget
Headline: The variance is timing, not proven efficiency. Evidence: Spend is 5% below plan because two hires started late.
29
Budget
Decision story — Spend is 5% below plan because two hires started late. Implication: The variance is timing, not proven efficiency. Keep the causal boundary explicit.
30
Budget
Chart narration — Spend is 5% below plan because two hires started late. Do not hide the counter-signal: The variance is timing, not proven efficiency.
31
Budget
Executive version — The variance is timing, not proven efficiency. Supporting evidence: Spend is 5% below plan because two hires started late.
32
Budget
Reader-question version — What should change next? The variance is timing, not proven efficiency. Evidence to keep visible: Spend is 5% below plan because two hires started late.
33
Reliability
Incident count fell, but total downtime rose because one event lasted much longer. Story: Counting incidents alone understates impact.
34
Reliability
Headline: Counting incidents alone understates impact. Evidence: Incident count fell, but total downtime rose because one event lasted much longer.
35
Reliability
Decision story — Incident count fell, but total downtime rose because one event lasted much longer. Implication: Counting incidents alone understates impact. Keep the causal boundary explicit.
36
Reliability
Chart narration — Incident count fell, but total downtime rose because one event lasted much longer. Do not hide the counter-signal: Counting incidents alone understates impact.
37
Reliability
Executive version — Counting incidents alone understates impact. Supporting evidence: Incident count fell, but total downtime rose because one event lasted much longer.
38
Reliability
Reader-question version — What should change next? Counting incidents alone understates impact. Evidence to keep visible: Incident count fell, but total downtime rose because one event lasted much longer.
39
Education
Completion is higher among checklist users, but use was voluntary. Story: The pattern supports further testing, not a causal claim.
40
Education
Headline: The pattern supports further testing, not a causal claim. Evidence: Completion is higher among checklist users, but use was voluntary.
41
Education
Decision story — Completion is higher among checklist users, but use was voluntary. Implication: The pattern supports further testing, not a causal claim. Keep the causal boundary explicit.
42
Education
Chart narration — Completion is higher among checklist users, but use was voluntary. Do not hide the counter-signal: The pattern supports further testing, not a causal claim.
43
Education
Executive version — The pattern supports further testing, not a causal claim. Supporting evidence: Completion is higher among checklist users, but use was voluntary.
44
Education
Reader-question version — What should change next? The pattern supports further testing, not a causal claim. Evidence to keep visible: Completion is higher among checklist users, but use was voluntary.
45
Research
Response rate improved, while one demographic segment remains underrepresented. Story: More responses do not remove the representativeness limitation.
46
Research
Headline: More responses do not remove the representativeness limitation. Evidence: Response rate improved, while one demographic segment remains underrepresented.
47
Research
Decision story — Response rate improved, while one demographic segment remains underrepresented. Implication: More responses do not remove the representativeness limitation. Keep the causal boundary explicit.
48
Research
Chart narration — Response rate improved, while one demographic segment remains underrepresented. Do not hide the counter-signal: More responses do not remove the representativeness limitation.
49
Research
Executive version — More responses do not remove the representativeness limitation. Supporting evidence: Response rate improved, while one demographic segment remains underrepresented.
50
Research
Reader-question version — What should change next? More responses do not remove the representativeness limitation. Evidence to keep visible: Response rate improved, while one demographic segment remains underrepresented.
51
Operations
Average queue length fell, but Monday peaks are unchanged. Story: The overall improvement does not solve the predictable weekly bottleneck.
52
Operations
Headline: The overall improvement does not solve the predictable weekly bottleneck. Evidence: Average queue length fell, but Monday peaks are unchanged.
53
Operations
Decision story — Average queue length fell, but Monday peaks are unchanged. Implication: The overall improvement does not solve the predictable weekly bottleneck. Keep the causal boundary explicit.
54
Operations
Chart narration — Average queue length fell, but Monday peaks are unchanged. Do not hide the counter-signal: The overall improvement does not solve the predictable weekly bottleneck.
55
Operations
Executive version — The overall improvement does not solve the predictable weekly bottleneck. Supporting evidence: Average queue length fell, but Monday peaks are unchanged.
56
Operations
Reader-question version — What should change next? The overall improvement does not solve the predictable weekly bottleneck. Evidence to keep visible: Average queue length fell, but Monday peaks are unchanged.
57
Content
Search exits fell, while zero-result searches stayed flat. Story: Navigation improved, but coverage gaps remain.
58
Content
Headline: Navigation improved, but coverage gaps remain. Evidence: Search exits fell, while zero-result searches stayed flat.
59
Content
Decision story — Search exits fell, while zero-result searches stayed flat. Implication: Navigation improved, but coverage gaps remain. Keep the causal boundary explicit.
60
Content
Chart narration — Search exits fell, while zero-result searches stayed flat. Do not hide the counter-signal: Navigation improved, but coverage gaps remain.
Turn an example into your own writing
Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.