Story points are Tableau's built-in tool for creating guided analytical presentations — a sequence of dashboard states, each making one point. This guide covers when story points are appropriate, how to structure a compelling analytical narrative, and the design patterns that make the difference between a story that informs and one that just shows data.
Tableau Story Points are the feature that most Tableau users know exists but rarely use well. They allow you to build a guided, sequential presentation from a series of dashboard states — annotated snapshots of your dashboards that walk a viewer through an analytical argument from beginning to conclusion.
Done well, a Tableau story is an analysis that speaks for itself. Done poorly, it is just a series of dashboards with text boxes. The difference is in whether the story is built around an argument or around a data dump.
What Story Points Are
A Tableau story is a workbook composed of story points — individual slides, each containing either a dashboard or a sheet. Each story point can have a caption: a short text that appears as the slide title and in the navigation at the top. The viewer clicks through story points sequentially, with a navigation strip showing all captions.
Story points are not videos or animations. They are static states that the viewer navigates manually. Unlike dashboards, story points do not support live interaction (no filter actions between story points, no parameter changes that persist across points). Each story point is a frozen configuration of a dashboard or sheet, with specific filters applied and specific marks selected or highlighted.
This constraint is important for the use case. A story is appropriate when you want to guide a viewer through a predetermined sequence of insights. A dashboard is appropriate when you want a viewer to explore data themselves. If the analytical goal is exploration, a dashboard serves better. If the goal is communication of a specific analytical conclusion, a story may be appropriate.
When Story Points Work
**Board presentations and executive briefings.** When you need to walk a leadership team through an analysis — "here is the problem, here is what we found, here is the recommendation" — a Tableau story provides structure. The viewer cannot get lost in filters. The flow is controlled. The presenter clicks through points while narrating.
**Embedded analytical reports.** When a report needs to tell a specific story and will be consumed without a presenter (emailed as a PDF or shared as a live workbook link), story points impose a reading sequence. The viewer can follow the intended argument without needing to know which chart to look at first.
**Training and tutorial content.** "Here is how to read this dashboard" built as a Tableau story, walking through each element in sequence, is a practical onboarding tool for complex analytical environments.
**Regulatory and audit reporting.** When an analytical conclusion needs to be documented with the evidence trail visible, a story that walks from raw data summary to conclusion to recommendation creates a documented reasoning chain.
Structuring an Effective Analytical Story
The most common mistake in story building is sequencing dashboards instead of sequencing an argument. "Here is the sales dashboard, here is the regional breakdown, here is the customer segmentation" is not a story — it is a tour. A tour is forgettable. A story makes a point.
Structure around the analytical argument:
**Point 1: The situation.** What is the current state? Establish the context with the key metric and the period. "Revenue grew 12% last year. But growth slowed significantly in Q4."
**Point 2: The complication.** What changed or what is the problem? "Q4 growth of 2% is the lowest quarterly rate in three years. This is not a seasonal effect — prior Q4s averaged 8% growth."
**Point 3: The analysis.** What does the data reveal about why? "The slowdown is concentrated in the Enterprise segment (down 4% QoQ) and in the APAC region (down 11% QoQ). SMB and other regions grew normally."
**Point 4: The implication.** What does this mean? "Two factors explain 80% of the Q4 slowdown: three large Enterprise renewals that slipped to Q1, and a sales capacity gap in APAC following two departures in October."
**Point 5: The recommendation.** What should happen next? "The renewal pipeline is recoverable — those three accounts are expected to close in Q1. The APAC capacity gap requires a hiring decision in the next 30 days to prevent Q1 risk."
Each story point advances the argument. The charts are evidence for the point being made, not the point themselves.
Technical Configuration
Each story point is created by dragging a sheet or dashboard onto the story canvas, then applying any filters or marks highlights specific to that point.
To capture a specific filtered state: apply the filter in the underlying dashboard, then click "Capture" in the story point to save the current state. The story point remembers the filter configuration at capture time.
To highlight specific marks: select the marks in the dashboard that should be highlighted, then capture. Tableau saves the selection state.
Captions — the text in the navigation strip — should be the point the story point makes, not a description of the chart. "Revenue slowed in Q4" rather than "Q4 Revenue Chart." The caption is what the viewer reads to orient themselves; make it work as a standalone summary of the point.
The story title (the workbook title visible at the top of the story) should be the thesis: "Q4 Slowdown: Causes and Recovery Outlook." Not "Sales Analysis" or "Q4 Review."
Design Constraints
Story points have design constraints that differ from dashboards. Dashboard layouts, floating objects, and container configurations all carry over to story points, but some interactive elements (filter actions between different story points, parameter persistence across story points) do not work as expected.
Avoid building story points that depend on the viewer interacting with the underlying dashboard. Viewers can interact — filters work, marks can be hovered — but interactions do not persist to the next story point. If the analysis depends on a filter being applied before a subsequent chart makes sense, either apply the filter at capture time or make the chart interpretable without the filter.
Font sizes that work on a dashboard at native resolution may not work when the story is displayed at a different screen size. Test the story on the display device (or display resolution) it will be used on before presenting.
Alternatives to Story Points
For presentations where you control the display (presenting from your own machine), Tableau dashboards presented through a browser with a slide-advancing keyboard shortcut often work better than story points — more interactivity is available, the layout is not constrained by the story canvas, and the presenter can respond to audience questions by modifying filters.
For documents that need to be shareable without a live Tableau Server connection, exporting dashboards to PDF and assembling them in PowerPoint or Keynote is common and avoids the technical requirements of a Tableau story (recipients need a Tableau viewer licence or a Tableau Public connection).
Story points occupy a specific niche — live, interactive analytical narratives that preserve interactivity within each point while controlling the overall flow. When that is the requirement, they are the right tool.
Our Tableau consulting practice designs both analytical dashboards and presentation-quality Tableau stories — contact us to discuss your Tableau development requirements.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →