Dashboards and Stories
Orchestrate views into a decision, not a gallery
A dashboard orchestrates worksheets into a decision page: layout containers, shared filters, and clear hierarchy. Stories turn that page into a narrative sequence for presentations.
What you will learn
- Build a dashboard with layout containers
- Wire filters across worksheets
- Create a story from dashboard snapshots
What is this?
A dashboard arranges worksheets, filters, parameters and text together using layout containers so the page resizes cleanly across devices. Filters placed on dashboards apply across sheets; highlight actions create cross-highlighting. A story arranges snapshots of dashboard states into an order that makes an argument for stakeholders.
Why do you need it?
- Stakeholders read pages, not sheets — a dashboard is the delivery unit.
- Containers mean the same dashboard looks right on a phone and a TV after a few minutes of layout.
- Cross-filtering is the cheapest interactivity that makes dashboards feel alive.
- Stories structure monthly reviews: what changed, why, what next.
Mental model
A news homepage editor
Dashboard design
An editor puts the headline above the fold, the lead article right beside it, and the sidebar for context — hierarchy, not equal-celled clutter. A story is the print edition's pagination: front page, business, sport, with the headline taking you to the detail.
How it works
- Layout containers hold charts; horizontal and vertical containers stack views automatically.
- Placing a dimension on the Filters shelf of a dashboard makes it a global control.
- Action filters let users click a bar and drill other views to that selection.
- Tooltips and highlight actions communicate state across worksheets.
- Stories store dashboard 'snapshots' — clipboard copies and step descriptions.
Dashboard assembly from worksheets.
Examples
One-filter literature flow
1. Dashboard > Layout: Header container + body container.2. Header: region filter + KPI cards.3. Body: line, bar, scatter in one horizontal container.4. Filter: apply the region control to 'All sheets using this source'.5. Actions: region filter also highlights the scatter.The header owns the shared decision lever; the body answers trend, compare and relationship questions; one control reaches every sheet and a highlight communicates cross-chart context.
In production
- An executive dashboard shows revenue, margin and pipeline cards on a header strip, with filters syncing every sheet.
- A field team builds a phone device dashboard with a compact thumbnail strip and drill-through.
- A quarterly review story walks 6 slides through actual vs plan, and the story still renders in a meeting room projector.
Best practices
- One decision per dashboard; title says the decision.
- Use containers over free-floating charts for responsive resizing.
- Gate global filters to the sheets they matter for.
- Keep the dashboard < 5 dominant visual regions for scanners.
Common mistakes
- Eight charts with no hierarchy scattered with no container.
- A filter that silently affects only one chart because it was bound to the sheet.
- Resizing everything on a touch device manually instead of using layout containers.
- A story that replays all views with no narrative order.
Common issues
Charts overlap when resizedFree-floating charts instead of layout containers
Wrap the charts in horizontal/vertical containers.
A filter changes only one sheetFilter scoped to that worksheet only
Set the filter to 'All using this data source' on the dashboard.
Story skips a step when resizedScreenshots tied to fixed sizes
Use dashboard snapshots based on containers, not fixed canvases.
Debugging tips
- Use the layout container outline (redrawn dashed lines) to see which container owns which chart.
- Preview a dashboard in 'Device Designer' to catch dead space early.
- Check filter 'apply to worksheets' to diagnose a silent unbound filter.
- Add a test highlight action and run the dashboard in Presentation mode.
Interview checkpoint
Quick quiz
What holds dashboard charts together so the page resizes cleanly?
A story stores live views that update when the data refreshes.