Tableau
Intermediate 13 min read Tableau

Tableau Dashboards

From sheets to a decision surface

Dashboards assemble sheets into a decision view: tiled vs floating layout, actions (filter, highlight, URL), device layouts, and performance hygiene so clicking feels instant.

dashboardactionsfilter actiontiled layoutdevice layoutstooltips
Prerequisites: Tableau Calculated Fields Tableau Overview
Before we start

What you will learn

  • Compose sheets into a coherent dashboard layout
  • Wire filter and highlight actions across sheets
  • Apply device layouts and performance hygiene
Introduction

What is this?

Tableau dashboards arrange sheets (and text/image/web containers) on a canvas — tiled (snap to grid) or floating (free placement). Actions connect sheets: clicking a bar filters or highlights tiles, opens a URL or a tooltip. Layout containers (horizontal/vertical) adapt across device layouts; performance hygiene (aggregate views, extract, relevant fields only) keeps clicks instant.

Motivation

Why do you need it?

  • A dashboard is where analysis becomes decisions — layout discipline is part of that.
  • Actions turn static tiles into one interactive, coherent answer.
  • Cross-device device layouts prevent a desktop dashboard breaking on mobile.
  • Slow dashboards kill adoption faster than any insight.
Think about it

Mental model

Imagine

A control room's panels wired to each other

Think of

A dashboard with actions

Each screen (sheet) shows one live reading. The room's value is the wiring: touch a region on the map and every other screen re-answers for that region. The control panel's buttons (actions) make the whole room explore—not just watch.

Mechanics

How it works

  • Tiled layout: dashboard items attach to a grid; floating objects sit at absolute positions.
  • Filter actions pass a value from a source sheet to a target sheet's filter.
  • Highlight actions emphasize matching marks; URL actions navigate.
  • Dashboard actions run run on click/hover/select with a defined target (sheet/dashboard/URL).
  • Device layouts define a separate optimized canvas per screen size for the same dashboard.

Action flow across dashboard tiles.

Source sheet
Filter action
Target sheets
Highlight
Response
Hands-on

Examples

The wiring that makes it feel native

The wiring that makes it feel native
Action: Filter
  Source : Sales by Region (dashboard)
  Target : Trend Sheet, Top-5 Sheet, KPI tiles
  Run On : Select
  Passed field: [Region] from the source sheet
 
Result: click EU => every tile recomputes for EU only;
  nothing to re-click, no rebuild, same numbers.

A single filter action makes the entire dashboard respond as one unit. Same pattern underlies highlight actions and tooltips.

Real world

In production

  • An ops war-room filters a live dashboard by clicking plant/site on a map, all metrics re-scope.
  • A sales dashboard exposes quarter and segment filters pinned to the top, driving every tile.
  • A mobile device layout hides heavy charts while keeping KPIs, so the exec gets a clean view.
Guidelines

Best practices

  • Keep one dashboard question; strip tiles that don't advance it.
  • Wire actions deliberately: select-triggered filter actions, not click-everywhere chaos.
  • Use layout containers over absolute floating to keep responsive resize sane.
  • Ship to a dashboard size the audience actually uses; test on the target device.
Watch out

Common mistakes

  • Every tile filtered independently — clicks don't cascade.
  • Too many sheets: beyond ~7 tiles attention and layout both break.
  • Floating objects everywhere: fine to pin, fragile to resize and mobile.
  • No performance pass — untimed sheets that load with a visible stagger.
When things break

Debugging tips

  • Action not firing → check Run On + target sheet + whether the source exposes the field.
  • Mobile breaks → give the dashboard a dedicated phone device layout and rebuild.
  • Slow load → aggregate/pre-extract; disable interactive tooltips and heavy URL actions.
Interviews

Interview checkpoint

Practice

Hands-on lab

Wire an Action-Driven Dashboard Flow
40 min · intermediate
In progress
Objectives
  • Model filter-action behavior in SQL
  • Reconcile KPI values after a region click
  • Simulate highlight (matching rows) logic

Wire an Action-Driven Dashboard Flow

40 min · intermediate

0/4 steps
0%
sandbox · Linux sandbox
$
Try these commands
Test yourself

Quick quiz

0/2
1

Clicking a bar that re-filters other tiles is implemented with:

2

A dashboard gains a dedicated layout per screen size via device layouts.

Go deeper

Official documentation

Create dashboards
docs
Actions - filter, highlight, URL
docs