Skip to main content
How a dashboard should be designed is covered in report writing concepts. Govern them with the standards below: which ones exist, who owns them, and what stops the set growing without limit.
Fill in the register and the rules below once, as a team. Everything here is a decision, not a rule handed down.

The rules

Four hold across every dashboard.
  1. Every dashboard reads from the flat file. Not from a platform connector, not from a separate export. A dashboard on its own data source will eventually disagree with a report, and there is no way to settle which is right.
  2. Every number traces to a row in the data dictionary. A metric on a dashboard that isn’t defined anywhere is a metric being invented in public.
  3. Every dashboard has one named owner. Not a team. The owner is a person even when an agent builds and refreshes the dashboard. Dashboards with no owner are the ones that break silently and stay broken.
  4. Every dashboard answers a stated question. Written on the dashboard itself, so a viewer knows what it’s for and a reviewer can tell whether it still does its job.

The register

One row per dashboard. This is the list that gets reviewed. Examples use Doughnut Labs, a SaaS company that sells disruptive Doughnut Technology. Delete them and fill in your own. Tiers match the KPI tiers in the dictionary. A dashboard mixing tier 1 outcomes with tracked diagnostics usually needs splitting, because the two have different audiences and different refresh needs.

Naming

A consistent name makes a dashboard findable in a tool that lists forty of them alphabetically. E.g. {account}_{scope}_{cadence}, lowercase with underscores: doughnutlabs_paid-media_daily. Scope is the area, not the tool. A dashboard named “Looker Studio copy 3” is a dashboard nobody will open.

Refresh and lag

A dashboard that silently serves stale data is worse than one that is visibly broken. People act on it. Showing the failure is the safer default.

Reviewing and retiring

Dashboards need maintenance in the opposite direction from most documents: the work is removing tiles, not adding them. At each review, per dashboard. The first two checks are mechanical, so the dashboard’s maintaining actor can run them each quarter and bring the answers; the rulings are the owner’s:
  • Has anyone opened it this quarter? Most tools can tell you.
  • Do the numbers still match the flat file? Reconcile one figure.
  • Does it still answer its stated question?
  • Which tiles have not changed a decision in a quarter? Delete them.
  • Is the owner still the right person, and still here?
Retire rather than delete. Mark it retired, note what replaced it, and keep the row. Otherwise the same dashboard gets rebuilt in six months by someone who assumed it never existed.

Before you build a new one

Check the register first. Most requests for a new dashboard are answered by an existing one, or by adding a filter to it. A near-duplicate dashboard splits the audience and doubles the maintenance, in the same way a near-duplicate landing page splits traffic. A dashboard whose stated question is already answered by the scheduled daily brief is a retirement candidate: “is today tracking normal?” arrives as a push, and dashboards earn their place below the brief’s grain, for on-demand exploration of why.
Type: standard
Domains: reporting
Provides: dashboard-standards
Uses: concept:reporting, data-dictionary, flat-file, kpi-definitions, process:daily-brief

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on October 30, 2026