"Dashboard" and "report" get used interchangeably. They shouldn't. Picking the wrong shape for a given question wastes time and produces output that nobody uses. Here's the distinction that actually matters.
Dashboards are for watching
A dashboard is something someone looks at regularly. The same person. With the same intent. Looking for changes from one viewing to the next.
Good dashboards have these properties:
- Few metrics. 5–10 widgets at most. More and people stop scanning.
- Stable layout. The MRR widget is in the same place every week. People develop visual memory.
- Comparable to last viewing. Time-series, period-over-period deltas, color-coded changes. The dashboard is built around "what's different from last time?"
- No commentary. The viewer brings the context.
Reports are for sharing
A report is something one person produces and sends to others, often once. The intent is to communicate a finding, decision or status.
Good reports have these properties:
- A narrative. Reports have a thesis. The charts support the argument.
- Context. What changed, why it matters, what we should do about it.
- Recipient-tailored. A board report and an engineering retrospective have different audiences. Different shape.
- Optionally frozen in time. The report shows the data as of when it was published. The reader isn't expected to refresh it.
Common mistakes
- Dashboard masquerading as report. "Here's our marketing dashboard, can you write the analysis?" — the recipient doesn't have the context to interpret it. A real report would walk through what to notice.
- Report masquerading as dashboard. A 30-slide deck that the team is expected to "check weekly". Nobody does. The metric you cared about is buried on page 14.
- Building a dashboard for a question only asked once. If the question won't come up again next month, write the report. Dashboards have maintenance cost.
- Writing a report for a question asked weekly. If you're producing the same report on a schedule, it's a dashboard with extra steps. Promote it.
The rule of thumb
If you'd benefit from seeing this changing over time, build a dashboard. If you need to persuade or inform someone of a finding, write a report. If you're not sure which one applies, you probably want a dashboard with a written summary — but pick one as the primary artifact.
clariBI handles both shapes. Auto-generated dashboards live in AI Dashboards; one-shot AI-narrated reports live in Reports. Use them for what they're designed for.