Ask a BI team what they would change about their estate and the answers are versions of one complaint: they cannot see what changed. A metric moved, a filter was added, a sheet was deleted — and the only record is the workbook itself, which the tool owns and nobody reads.
What a dashboard is, if you strip the tool away
A layout. A list of charts. For each chart: what to ask — which measures, broken down by what, filtered how — and how to draw it. That is the whole thing.
Written down plainly, a dashboard is a short, readable document that a business analyst can open, understand and compare with last month's version. Here is a real panel's definition, shown in the console next to the chart it produces:
Opaque XML or a binary. Diffing two versions is impossible, reviewing a change is impossible, and only the tool that made it can write one.
A readable structure naming metrics, dimensions and filters. It can be diffed, reviewed, generated, promoted between environments, and edited by hand.
Three things follow from treating that document as the product rather than as an export.
1. It can be reviewed
A change that swaps net revenue for gross revenue on one chart is a one-line difference. A reviewer sees it. In a workbook the same change is a re-saved file and a commit note that says “updated dashboard”.
Every version published here carries a note; restoring an earlier one is a click.
2. It can be written by the assistant — and by a person, afterwards
Once a dashboard is a document, the assistant can draft one. “A monthly sales overview for the leadership meeting — headline numbers, the trend, and a breakdown by region and category” becomes eight panels written into the same document a person edits in the console.
There is no second, special path for generated content. That is also why it is safe: the assistant produces a description of what to show, never software that runs in your browser.
flowchart LR
A["Describe it
in a sentence"] --> DOC["One dashboard document"]
B["Design it
field by field"] --> DOC
C["Import it
from a workbook"] --> DOC
DOC --> V["Versioned + reviewable"]
DOC --> E["Edited by hand, any panel"]
DOC --> P["Promoted dev → prod"]
style DOC fill:#e6f7f2,stroke:#9fd8c9
Charts are descriptions for the same reason
A chart here is a description — the type, what goes on each axis, what the colours mean. The console draws it with the product's palette and rules. Descriptions can be saved, versioned, reviewed and trusted. Generated code cannot.
flowchart LR
D["Draft"] --> R{"Review
the diff is four lines"}
R -->|"approved"| P["Publish
version + note"]
R -->|"rejected"| D
P --> L["Live"]
L -->|"something is wrong"| RS["Restore any
earlier version"]
RS --> L
P --> PR["Promote dev → prod
definitions travel with it"]
style R fill:#fff4e6,stroke:#f0cb9a
style P fill:#e6f7f2,stroke:#9fd8c9
3. It can be promoted like any other controlled change
Draft, review, publish. A dashboard moves between environments the way a policy document does, and the business definitions it relies on travel with it. This is the property engineering-led organisations keep asking Tableau for and cannot get.
| Practice engineers already have | Applies to a document | Applies to a workbook |
|---|---|---|
| Code review before it ships | Yes — the change is readable | No — nothing to read |
| Diff two versions | Yes | No |
| Roll back a bad change | One click, with the note that explains it | Restore a file, if someone kept one |
| Promote dev → prod | The document and its definitions move together | Re-publish and hope |
| Generate or edit programmatically | Yes | Only the tool can write it |
What it costs
A document-first dashboard is deliberately simpler than a workbook that has grown for a decade. Dual axes, custom shapes, pixel-perfect crosstabs — some of that we chose not to support, and some we have not built yet.
The dual-axis omission is a choice rather than a gap. Two measures on two different scales in one frame is the most common way to make a chart imply a relationship that is not in the data, and the fix is nearly always two charts or one indexed to a common base.
The trade is a smaller, reviewable surface that an assistant can operate safely. For most dashboards in most estates, that is the better deal — but it is a trade, and it is worth checking against your own worst workbook.
What a document lets a panel tell you about itself → · The full business case →