Designing dashboards for executives vs analysts

You can spot the dashboard built for everyone: it lives in slide decks. People screenshot it, paste it, and never open the real thing again. Executives found it dense. Analysts found it shallow. Nobody said so out loud.

These are two products, not two tastes. An executive scans a handful of outcome metrics to decide whether to act or ask a sharper question. An analyst opens the same data to find out why something moved. Serving both on one screen usually serves neither — the same principle behind what makes a good dashboard at all.

What the executive is deciding

One question, fast: is the business on track, and if not, where. Not the full picture — the few numbers that signal whether to intervene, plus enough context to know what to ask next. That means a small set of outcome metrics against a target or a prior period. Revenue against plan. Churn against tolerance. A trend line that shows direction.

The read should take seconds and end in a decision or a better question, never a research session. Density is the enemy here: every extra metric competes with the three that matter. If an executive has to hunt for the signal, the screen has failed at its only job.

What the analyst needs instead

They start where the executive stops. A number moved; now find the cause. That needs granularity, breakdowns, and freedom to slice along any dimension — region, cohort, channel, window. Filter, compare, export, without asking anyone for help.

For that reader density is a feature, not clutter. It is the workspace. The aggregation that helps an executive read faster actively obstructs an analyst, because it hides exactly the detail they came for. A summary answers a question; a table lets you ask your own. Most teams building dashboards confuse the two.

Five things that change between them

• Executive: five to nine outcome metrics against targets. Analyst: dozens, broken down by dimension.
• Executive: high aggregation, one default view. Analyst: raw granularity, saved views, custom filters.
• Executive: minimal interaction, read in seconds. Analyst: filter, pivot, drill, export.
• Executive: status and trend — on track or not. Analyst: distributions, segments, correlations that explain it.
• Executive: opinionated defaults that hide complexity. Analyst: a neutral surface that exposes it.

Serving both without building twice

Layer it. The top layer is the executive view — a few outcome metrics against targets, readable in seconds. Every one of those figures is a door: click it and you drop into the analyst layer, where filters, breakdowns and exports live.

The default stays calm while the full depth sits one interaction away. Both audiences share one source of truth, so the summary and the detail never disagree, and each meets it at the level their job needs. Getting those seams right — what surfaces by default, what waits for a click — is the centre of our dashboards and data design.

It also settles the political fight that sinks most dashboard projects. Nobody loses their metric. The analyst's forty fields still exist; they simply live beneath the executive's nine instead of competing with them on the front page.