data-narrative-builder
Data Narrative Builder
When to use
- A presentation exists but feels like a data dump rather than a story
- The analysis has a clear finding but the team doesn't know how to make it compelling
- The audience is senior and will not read more than 5 slides
- A decision needs to be made and the data needs to make a clear, emotion-aware argument
- A recurring report needs to be restructured around a narrative rather than a metric list
Process
- Identify the central message — write the single most important thing the audience should know and do after seeing this. Everything else is supporting material. If there's more than one message, there are multiple presentations.
- Choose a narrative framework — select the structure that fits the context. Situation–Complication–Resolution works for most problem/solution stories. Before–After–Bridge is strong for demonstrating impact. See
references/narrative_frameworks.mdfor all patterns with examples. - Assign an emotional arc — map each section to an intended emotional state: establish comfort (Situation), introduce tension (Complication), offer confidence (Resolution). Tone and data emphasis should match the intended emotion at each stage.
- Draft each section with data woven in — apply the pyramid principle: lead with the conclusion, then support it with evidence. Numbers must serve the narrative, not interrupt it. Round large numbers for recall; humanise by expressing impact in terms the audience cares about.
- Plan the visual sequence — assign one key chart or visual to each narrative beat. The visual should reinforce the spoken or written message, not repeat it. See
references/data_writing_guide.mdfor annotation and emphasis techniques. - Write the opening hook and closing call to action — the hook must earn attention in under 10 seconds (a surprising stat, a question, or a contrast). The CTA must name a specific decision, person, and deadline. Complete
assets/narrative_template.md.
Inputs the skill needs
- The central finding or insight to be communicated
- The audience (role, knowledge level, what they care about most)
- The desired action or decision at the end of the presentation
- All supporting data and charts already prepared
- Format and time constraints (slides, report, 5-minute presentation, 30-page doc)
Output
references/narrative_frameworks.md— SCR, BAB, hero journey, and sparklines patterns with data storytelling examplesreferences/data_writing_guide.md— pyramid principle, number formatting, annotation, plain-language techniquesassets/narrative_template.md— fill-in-the-blank narrative structure: hook, situation, complication, resolution, call to action
More from nimrodfisher/data-analytics-skills
funnel-analysis
Conversion funnel analysis with drop-off investigation. Use when analyzing multi-step processes, identifying conversion bottlenecks, comparing segments through a funnel, or optimizing user journeys.
37metric-reconciliation
Cross-source metric validation and discrepancy investigation. Use when metrics from different sources don't match, investigating data quality issues between systems, or validating data migration accuracy.
31insight-synthesis
Transform data findings into compelling insights. Use when converting analysis results into actionable insights, connecting findings to business impact, or preparing insights for stakeholder communication.
31dashboard-specification
Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
30data-quality-audit
Comprehensive data quality assessment against business rules, schema constraints, and freshness expectations. Activate when validating data pipeline outputs before production use, auditing a dataset against defined business rules, or producing a quality scorecard for a data asset.
30time-series-analysis
Temporal pattern detection and forecasting. Use when analyzing trends over time, detecting seasonality, identifying anomalies in time series, or building simple forecasting models for planning.
30