Tableau Overview and the Viz Grammar
Fields to shelves to insights
Tableau lets you drag fields onto shelves and automatically picks a Schema-aware encoding: pills, marks, rows/columns, color, size, tooltip. The product line spans Desktop, Prep, Server/Cloud and embedded views.
What you will learn
- Map Tableau's shelves and pill types to the chart-grammar model
- Understand dimensions vs measures and discrete vs continuous
- Navigate Desktop, Prep, Server/Cloud and embedded surfaces
What is this?
Tableau expresses charts declaratively: you drag fields onto shelves (Rows, Columns, Color, Size, Filters) and Tableau renders the appropriate mark automatically. The two big axes are dimension vs measure (categorical vs numeric) and discrete vs continuous (pills: blue = discrete, green = continuous). Everything else — filters, parameters, sets, calculated fields — modifies that base grammar.
Why do you need it?
- The grammar means you switch from building each chart to describing an answer.
- It forces a precise vocabulary (measure, dimension, discrete, continuous) that interviewers test.
- Understanding shelves explains why some drags display helpfully and others error.
- The same grammar underlies dashboards, so mastery compounds.
Mental model
A guitar's tuning and frets
Tableau shelves and pills
The guitar (grammar) is fixed — strings (dimensions/measures) and frets (shelves). You don't build a new instrument per song; you place your fingers (pills) differently to get a different chord. Knowing which fret is a 'dimension shelf' tells you what the sound will be before you strike.
How it works
- A data connection defines fields; Tableau auto-types them as dimension or measure.
- Dropping a dimension on Rows/Columns creates the axis headers; a measure creates an aggregate axis.
- Blue pills are discrete (headers/categories), green pills continuous (axes/scales).
- The Marks card controls color, size, shape, label and tooltip encodings per mark.
- The resulting mark type (table, bar, line, circle, map) adapts to the shelf layout and fields.
Fields → shelves → rendered marks.
Examples
Two pills are a bar chart
Sheet layout: Columns : [Region] (blue pill, discrete) Rows : SUM([Sales]) (green pill, continuous) Result: One bar per region, height = summed sales. Drag [Sales] to Color => bars become bi-colored by magnitude.Dimension to columns gives category headers; measure to rows aggregates. Every Tableau sheet is this same pattern recombined.
In production
- A regional sales view reuses one drag (Region, SUM Sales) for multiple mark types with color/size restated.
- An analyst switches continuous to discrete to turn a line-axis trend into a banded heatmap.
- A viz author exports the same underlying sheet to a dashboard tile, filtered by shared filters.
Best practices
- Keep one 'source of truth' sheet per metric family; build dashboards from those tiles.
- Name fields and aliases clearly; rename pills you ship to stakeholders.
- Know when pills are blue vs green — it predicts the axis behavior instantly.
- Start with the question, then place fields: don't add shelves speculatively.
Common mistakes
- Confusing dimension/measure, so an ID aggregate where a category belongs.
- Green/blue misuse — e.g. leaving a dimension continuous and getting a gradient axis.
- Over-encoding: color + size + shape with no hierarchy = a noise chart.
- Dragging to every shelf 'just to see' and losing the deliberate message.
Debugging tips
- Axis counts instead of headers → the field is a measure being summed; change to dimension.
- Chart type wrong → the pill color/intent unsets; switch discrete/continuous.
- Filters seem ignored → a measure filter vs dimension filter vs context filter distinction.
Interview checkpoint
Quick quiz
In Tableau, a blue pill typically means the field is:
Tableau auto-selects a mark type based on the shelf layout.