Story First, Data Second (Storyboard Before You Build)
The Problem
Project kickoff: "Build a sales dashboard." Team immediately opens Tableau. Starts dragging fields. Builds 6 charts. Spends 40 hours. Presents to stakeholders. Response: "This is nice, but it doesn't answer my questions." Why? Because you built data visualizations, not a story. You threw charts at a problem without understanding the narrative. What decision are they making? What question needs answering? What's the tension? The solution? You skipped all that and went straight to building. It's like a manufacturing plant starting production without a blueprint—you'll build something, but probably not what's needed.
The Principle
Storyboard first, build second. Before touching any tools, grab a pencil and sketch: What's the hook? What tension exists? What solution are you offering? What proof matters? How does it close? Map the narrative arc: Hook → Set Stage → Create Tension → Offer Solution → Provide Proof → Close with action. Then translate that story into data visualizations. Each chart should serve a part of the story. The magic happens when your dashboard tells a story, not just shows data. Think manufacturing: you don't start welding metal until the blueprint is done. Same with analytics—storyboard the narrative before building the viz.
3 Steps to Take Action
- 1
**Mandatory Storyboard Session** Before building ANY executive presentation: - Gather stakeholders - Grab pencils, post-its, whiteboard - Map the story arc: * Hook: Why should they care? * Set stage: What's the context? * Tension: What's the problem? * Solution: What are you proposing? * Proof: Why will it work? * Close: What's next? Spend 60-90 minutes. Don't touch data tools yet. Output: 6-8 post-its with key beats of the story.
- 2
**Map Data to Story Beats** For each story beat: - What data supports it? - What visualization type? (one number? trend? comparison?) - What's the main point? (write it in one sentence) Example: - Tension beat: "Problem is growing" - Data: Member coverage gaps over time - Viz: Line chart showing 40% increase - Point: "Coverage gaps up 40% in 18 months" Rule: Each chart must serve a story beat. If it doesn't, cut it.
- 3
**Test the Narrative** Before building: - Walk through the storyboard with someone unfamiliar - Ask: "Does the story flow? Is anything missing? Confusing?" After building: - Show to a test audience - Ask them to summarize the main point - If they can't, the story failed Goal: Anyone should be able to follow the narrative without explanation. Bonus: Storyboards cut build time 50% (because you know exactly what to build and why).
💡 Inspired By
Nancy Duarte's storytelling framework. Cole Nussbaumer Knaflic's "Storytelling with Data." a Fortune 10 healthcare company storyboarding practice (2019-2025).
This is what Analytics Pitfalls & Principles is about: people helping people.
In Practice
A Fortune 5 healthcare company's team got a request: "Show impact of coverage gaps on members." They almost started building dashboards. Instead, new leader said: "Storyboard it first." They grabbed pencils and post-its: Hook (member John's story of coverage gap), Set stage (how common is this?), Tension (growing problem, financial impact), Solution (proposed fix), Proof (pilot results), Close (next steps). Took 90 minutes. Then built the presentation: 1 slide per story beat. 6 slides total. 3 charts. When presented: exec team immediately understood, asked strategic questions, approved budget on the spot. Old approach would've been 20 slides of data with no narrative thread. The storyboard forced clarity: what's the ONE thing we're trying to communicate? Everything else fell into place. Time to approval: 1 meeting (vs typical 3-4). Storyboarding became mandatory for all executive presentations.
