← All Episodes

Episode 9

Data Storytelling

35 min

About This Episode

In episode 9 of Data & AI Heads, host Ian Allison speaks with Brent Dykes, author of "Effective Data Storytelling" and founder of Analytics Hero, about what separates genuine data storytelling from the noise. Brent explains why data visualization alone is not a story, why dashboards are monitoring tools rather than storytelling vehicles, and how a structured narrative arc rooted in real insights is what actually moves decision makers to act.

Drawing on Freytag's dramatic arc, Disney's storyboarding process, and the psychology of Daniel Kahneman's System 1 and System 2 thinking, Brent outlines a practical framework: start with a hook tied to an observation in the data, build toward an "aha moment" that delivers the core insight, and close with clear options and recommendations for decision makers. He also addresses the neuroscience behind why presenting bare facts can trigger a defensive reaction in audiences, and how packaging findings as a narrative lowers that guard.

Brent also discusses his masterclass course at effectivedatastorytelling.com, which covers five modules including narrative, visualization, and application, and is designed for individuals and smaller teams who cannot access his enterprise workshop format. This episode is essential listening for data professionals who want their analysis to drive real organizational change rather than disappear into a dashboard.

Key Takeaways

  1. Data visualization is a component of data storytelling, not a substitute for it. A single chart or a dashboard rarely constitutes a complete story.
  2. Dashboards are monitoring and exploration tools that can surface anomalies worth investigating, but the story only begins after analysis reveals a genuine insight.
  3. A strong data story follows a narrative arc: a hook that captures attention, a build-up through supporting findings, an aha moment that delivers the core insight, and a close that presents clear options and recommendations.
  4. The insight at the center of a data story should represent an unexpected shift in understanding, something the audience did not know about customers, competitors, or internal processes, paired with a clear so-what for decision makers.
  5. Avoid narrating the journey to the insight. Business audiences do not need to hear about data cleansing steps or analysis methods. The story should be oriented around business impact, not the analyst's process.
  6. Storyboarding the narrative before building visualizations, a technique adapted from Disney's animation process, prevents wasted effort and ensures the story structure is sound before visual polish begins.
  7. Presenting raw facts that conflict with a decision maker's existing viewpoint can trigger a fight-or-flight defensive reaction in the brain. Framing findings as a narrative lowers that guard and makes audiences more open to new perspectives.
  8. Understanding the audience's priorities, KPIs, and current resource commitments before crafting a data story is essential to keeping the narrative focused and relevant.

What We Cover

What data storytelling actually is versus common misconceptions The role of dashboards in the analytics workflow Applying Freytag's dramatic arc to data presentations The storyboarding process adapted from Disney animation Psychology of decision making: System 1, System 2, and narrative Pre-attentive attributes, color, and gestalt principles in data visualization Structuring the aha moment and recommendation for executive audiences Data storytelling training: workshops and masterclass options

Frequently Asked Questions

What is the difference between data visualization and data storytelling?

Data visualization is one component of data storytelling, but it is not the whole thing. Effective data storytelling also requires a central insight, a narrative arc that gives context and builds to an aha moment, and clear recommendations that equip decision makers to act. A single chart or a polished dashboard does not constitute a story on its own.

Can a dashboard tell a data story?

According to Brent Dykes, dashboards do not tell stories. They are valuable tools for monitoring key metrics and surfacing anomalies that may be worth investigating, but the story only forms after further analysis reveals a genuine insight. Dashboards can set up potential stories and later serve as a tracking mechanism after a decision has been made, but they are not a storytelling format.

What narrative structure should a data story follow?

Brent Dykes recommends adapting Freytag's dramatic arc, used in Shakespearean plays, to data presentations. The structure starts with establishing context and a hook tied to an observation in the data, builds through supporting analysis steps toward an aha moment that delivers the core insight, and closes with two or three options and a recommendation for decision makers. The number of steps between the hook and the aha varies based on the complexity of the analysis.

Why do facts alone often fail to persuade decision makers?

Research cited by Brent Dykes shows that when people encounter data that conflicts with their existing viewpoint, the brain registers a reaction similar to encountering a physical threat, triggering a defensive, fight-or-flight response. Packaging the same information inside a narrative lowers that guard, makes audiences more open-minded, and increases the likelihood they will genuinely consider a different perspective.

What is the storyboarding process in data storytelling and why does it matter?

Storyboarding, adapted from the process Disney developed for animated films, means sketching out the narrative structure before building any data visualizations. Brent Dykes recommends this because analysts often waste significant time polishing visuals before confirming that the underlying story is coherent. Working out the hook, the aha moment, and the recommendations first ensures the narrative is sound before visual development begins.

How should data analysts decide what to include or cut from a data story?

Brent Dykes advises starting by deeply understanding the audience: their priorities, KPIs, current investments, and the outcomes they are trying to drive. Anything that does not advance the narrative from the hook to the aha moment should be removed. A common mistake is narrating the analyst's journey to the insight, including data cleansing steps and methodology, which business audiences generally do not need or want.

How does psychology inform effective data visualization design?

Brent Dykes draws on several psychological frameworks when designing visuals. Gestalt principles from early 20th-century German psychology explain how people group information by proximity and similarity. Pre-attentive attributes such as color and size explain why certain visual elements immediately draw the eye. And Kahneman's System 1 thinking, the brain's fast, pattern-seeking mode, highlights why visuals that leverage pattern recognition help audiences follow a data story more naturally.

About the Guest

Brent Dykes

Brent Dykes is the author of "Effective Data Storytelling" and the founder of Analytics Hero, a company focused on helping organizations communicate data insights more effectively. He began presenting on data storytelling at Adobe Summit in 2014, where his sessions became among the most popular at the conference, and has since delivered workshops and keynotes at numerous industry events. Brent offers enterprise workshops covering narrative and visualization, as well as a multi-module masterclass course available at effectivedatastorytelling.com, designed for individuals and smaller teams. His work draws on literary narrative theory, Disney's storyboarding methodology, and behavioral psychology, including the research of Daniel Kahneman and Antonio Damasio, to help data professionals bridge the gap between analysis and decision-making.

Connect on LinkedIn →

More Episodes