24 Using Stories to Make Dashboards

What This Chapter Covers

A Tableau Story is a sequence of Story Points, individual “slides” containing a worksheet or dashboard, each with a caption and an optional navigation pane. Stories transform analytical findings into guided, presentation-ready narratives, bridging the gap between the exploratory dashboard (where the analyst discovers insights) and the communicative presentation (where the analyst shares insights with a decision-making audience). This chapter covers the Tableau Story interface, how to structure a compelling data story, best practices for story captions and annotations, and the principles of data storytelling that make the difference between a story that informs and one that influences.

flowchart LR
    A[Analytical <br> Findings] --> B[Story <br> Structure]
    B --> C[Story Point 1 <br> Context / Setup]
    C --> D[Story Point 2 <br> Conflict / Finding]
    D --> E[Story Point 3 <br> Resolution / Action]
    E --> F[Story Point 4 <br> Evidence / Detail]
    F --> G[Published <br> Narrative]
    style A fill:#e3f2fd,stroke:#1976D2
    style D fill:#fce4ec,stroke:#C62828
    style G fill:#e8f5e9,stroke:#388E3C

24.1 The Tableau Story Interface

Creating and Navigating Stories

Create a Story by clicking the New Story button at the bottom of the workbook (the icon showing a stacked-page symbol). The Story workspace has the following components:

Story panel (left): Lists all sheets (worksheets and dashboards) available to add to story points. Drag any sheet to the story canvas to add it as a story point.

Story point navigator (top): Shows the sequence of story points as a row of captioned boxes. Click any box to navigate to that story point. Click the “+” button at the end to add a new blank story point.

Story canvas (centre): Shows the content of the currently selected story point, a worksheet or dashboard embedded in the story frame.

Caption box (below the navigator): Each story point has a caption, a short text label displayed in the navigator box. Double-click the caption in the navigator to edit it. Caption text should be a declarative finding statement (not “Slide 3” or “Revenue”, but “Revenue Rebounded in Q4”).

Story size: Like dashboards, stories have a fixed size. Set via the Story panel > Size dropdown. For presentation use, 1200×900px is a common choice. For embedded web display, match the embedding container dimensions.

[Insert screenshot of the Tableau Story workspace showing the story panel on the left, the story point navigator at the top with three captioned boxes, the canvas showing a dashboard, and the caption box highlighted below the navigator]

Story Point Types: Blank vs. Duplicated

Each story point can be one of two types:

Blank story point: A fresh instance of the selected sheet, reset to its default state (all filters cleared, no selections). Use for story points that should start with a “clean” view before the presenter guides the audience’s attention.

Duplicated story point: A copy of the current story point’s state, preserving the exact filter selections, highlighted marks, and annotation positions of the current view. Use when you want to show the same chart in multiple states in sequence (e.g., first show the overall trend, then duplicate the point and filter it to highlight one category’s contribution).

Adding a duplicated story point: With a story point selected, click Duplicate (in the story point navigator) to create an exact copy. Then change the filter or annotation state on the copy, the original remains unchanged.

Caption sequences: Use sequential captions to create a structured narrative thread: “1. Overall revenue is growing” → “2. Technology is driving the growth” → “3. But profitability is declining in Technology” → “4. The issue is concentrated in Q3 discounting”.

24.2 Structuring a Data Story

The Three-Act Data Story Structure

Effective data stories follow a narrative structure, the same three-act structure that makes any compelling story work: Setup, Conflict, and Resolution.

Act 1, Setup (Context): Establish the context that makes the audience care. What is the business situation? What metric are we examining, over what period, and why does it matter? The setup story point typically shows a broad, reassuring view (e.g., overall business is healthy, revenue is growing), this is the “normal” state that makes the subsequent conflict meaningful.

Act 2, Conflict (The Finding): Introduce the finding that disrupts the normal state. This is the analytical insight, the pattern, anomaly, or trend that demands attention. The conflict story points typically show progressively deeper drill-downs: starting with the category-level breakdown that reveals the problem, then the geographic or temporal concentration, then the specific driver.

Act 3, Resolution (Recommendation): Connect the finding to a recommended action. Data stories that end with “here is the problem” without a resolution leave the audience uncertain about what to do. The resolution story point articulates the business implication and the recommended response.

Example story arc for the Superstore data: 1. “Overall FY2023 revenue grew 8% YoY, strong performance.” (Setup) 2. “But profit margin declined from 12% to 9% despite revenue growth.” (Conflict introduced) 3. “The margin decline is entirely in Technology, driven by Q3 discounting.” (Conflict deepened) 4. “9 customers in the East received >40% discounts on machines in Q3.” (Root cause) 5. “Recommendation: Cap Technology discounts at 25% for the East region in H2.” (Resolution)

The Setup-Complication-Resolution-Recommendation Framework

An alternative to the three-act structure is the SCRR (Setup, Complication, Resolution, Recommendation) framework, widely used in management consulting:

Setup: “Our revenue is growing, we are on track for our annual target.” (2 slides maximum, this is not the interesting part.)

Complication: “However, all of the revenue growth is coming from a segment that generates below-average margin.” (The surprising finding that creates urgency.)

Resolution: “Our analysis shows the margin pressure is driven by a specific promotional programme in Q3.” (The analytical explanation of why the complication exists.)

Recommendation: “Restructuring the Q3 promotional framework can recover 3 percentage points of margin without sacrificing revenue growth.” (The action, quantified.)

The SCRR framework is valuable because it separates what happened (Complication) from why it happened (Resolution) from what to do about it (Recommendation), three questions that require different types of evidence and analytical work.

24.3 Story Captions and Annotations

Writing Effective Story Captions

The story caption (displayed in the navigator box at the top of the story) is the sentence the presenter will say out loud when this slide appears. Write captions as complete declarative sentences that state the finding, not as labels or topics.

Caption quality test: Read the captions of all story points in sequence without looking at any charts. If the captions tell a complete, coherent analytical narrative, they are well-written. If they are just chart labels (“Revenue”, “By Region”, “Q3 Detail”), the story structure is unclear.

Caption length: 10–15 words maximum. Long captions are difficult to read at presentation speed. The caption is a headline, the chart provides the evidence.

Examples of weak vs. strong captions:

Weak Caption	Strong Caption
“Revenue Chart”	“Revenue grew 8% YoY”
“Technology Analysis”	“Technology drove all revenue growth”
“Q3 Detail”	“Q3 margin decline concentrated in East”
“Recommendation”	“Capping discounts at 25% recovers 3pt margin”

Adding Story-Specific Annotations

Each story point can have annotations that are specific to that point, the same chart can appear in multiple story points with different annotations on each, progressively revealing information.

Building a progressive annotation sequence: 1. Story Point 1: Show the chart with no annotations. Caption: “Overall revenue is growing.” 2. Duplicate to Story Point 2. Add an annotation on the Technology line: “Technology outpaces other categories.” Caption: “Technology is the primary growth driver.” 3. Duplicate to Story Point 3. Add a second annotation on the Q3 Technology dip: “Margin compressed in Q3.” Caption: “But Technology margin declined sharply in Q3.”

Each duplication preserves the previous state (including the annotation from Step 2) and adds the new annotation. The audience sees the story building progressively, not all annotations at once, which would be confusing.

[Insert screenshot of a story navigator showing three story points with captions “Revenue growing”, “Technology leads”, “Margin concern”, and the canvas showing the third point with two annotations visible on the chart]

24.4 Publishing and Presenting Stories

Publishing a Story to Tableau Server

Tableau Stories are published to Tableau Server or Cloud in the same way as workbooks. The published story is fully interactive, audiences can navigate between story points, hover for tooltips, and (if actions are configured) interact with the embedded charts.

Presentation mode on Tableau Server: When viewing a published story on Tableau Server, click the Full Screen button (or press F11) to enter presentation mode. The navigator disappears, and the story fills the screen. Story point navigation is available via keyboard arrows or by clicking the left/right arrows at the edges of the screen.

Exporting stories to PowerPoint: Tableau can export a story as a PowerPoint presentation. File > Export > PowerPoint. Each story point becomes a separate slide with a screenshot of the view. This produces a static (non-interactive) presentation file, useful for sending to audiences without Tableau access.

Exporting to PDF: File > Print to PDF. Each story point becomes a page. Useful for formal written report delivery.

Export Format	Interactive	Use Case
Tableau Server (published)	Yes	Live presentation, self-service exploration
PowerPoint (.pptx)	No	Email distribution, formal presentations
PDF (.pdf)	No	Printed reports, regulatory submissions

24.5 Data Storytelling Principles

Principles of Effective Data Storytelling

Data storytelling is the practice of combining data, visuals, and narrative to communicate insights that drive action. Three principles distinguish effective data storytellers:

Principle 1, Audience-first design. Every story decision should be made with a specific audience in mind. A story told to the CFO has different content, depth, and vocabulary than the same story told to the operations team. The CFO story leads with financial impact and strategic recommendation; the operations story leads with process metrics and operational root causes. Know your audience before building your story.

Principle 2, Curated, not comprehensive. A data story is not a data dump. The analyst has typically examined dozens of charts and hundreds of data points to find the insight. The story shares the 3–4 charts that build the case for the insight, not all 40 charts explored along the way. Showing comprehensive data signals analytical insecurity; showing curated data signals analytical confidence.

Principle 3, Insight leads, evidence follows. In data storytelling, structure the argument as “Here is what is true, and here is the data that proves it”, not “Here is all the data, please form your own conclusion.” State the insight in the caption; use the chart as evidence. This is counterintuitive for analysts trained to “let the data speak”, but decision-makers respond to conclusions backed by data, not data searching for conclusions.

The Attention-Interest-Desire-Action Framework for Data Stories

Borrowed from marketing communication, the AIDA framework provides a structure for data stories intended to drive a specific decision or action:

Attention: Open with a striking data point or a chart that reveals an unexpected pattern. This should be provocative enough that the audience immediately wants to know more. “Last quarter, we left $2.3 million on the table due to preventable order returns.”

Interest: Show the analytical depth behind the opening claim. Drill into the data to demonstrate that the finding is real, significant, and non-obvious. Show the segment breakdown, the geographic pattern, the trend over time.

Desire: Connect the finding to an outcome the audience cares about. Frame the analysis in terms of the business value of acting on the recommendation. “Reducing return rates by 50% would recover $1.2M in annual revenue and improve NPS by an estimated 8 points.”

Action: Close with a specific, actionable recommendation with a named owner and a timeline. “We recommend that the Operations team review the top 5 product categories by return rate and implement a quality check protocol before the Q4 peak season.”

24.6 Summary

Key Concepts at a Glance

Topic	Key Technique	Access Point
Story creation	New Story tab	Bottom tab bar > New Story icon
Story points	Blank (fresh) or Duplicated (preserved state)	Story navigator > Add / Duplicate
Declarative captions	Finding statements, not topic labels	Double-click caption box in navigator
Three-act structure	Setup → Conflict → Resolution	Story design principle
SCRR framework	Setup, Complication, Resolution, Recommendation	Consulting narrative structure
Progressive annotation	Add annotations per duplicated story point	Annotate on each duplicate independently
Export to PowerPoint	Static screenshot slides per story point	File > Export > PowerPoint
AIDA framework	Attention, Interest, Desire, Action	Presentation structure for decision-driven stories
Audience-first design	Content decisions driven by audience profile	Design principle, not a Tableau feature

Applying This in Practice

The most common mistake analysts make when presenting data is spending 80% of the presentation on methodology (“how we collected and cleaned the data”) and 20% on the finding. For an executive audience, invert this ratio: 20% on the analytical approach (one sentence or one slide) and 80% on the finding, its implications, and the recommended action. The audience is not evaluating your data work; they are making a business decision. Respect their time by leading with the conclusion and using the data as evidence, exactly the structure that Tableau Stories support when designed with the SCRR or AIDA framework.