Data & AnalyticsIntermediate1-2 days initially

Dashboard Design

A dashboard is not every metric on one screen; it helps a specific role answer a specific question. This skill fixes the user and decision, then chooses metrics, charts and refresh cadence.

Workflow

  1. 1

    Define user and decision

    State who views it, in what context and what decision they make afterward. One dashboard serves one role and one decision; do not try to satisfy executives, operations and finance at once.

  2. 2

    Choose 5-9 core metrics

    Use three layers: outcome, driver and health metrics. For each, define calculation, target and alert threshold. Remove metrics with no decision use.

  3. 3

    Choose the right chart

    Use lines for trends, bars for comparison, stacked bars for composition and histograms for distribution. Avoid dual axes and 3D pies; use color for state, not decoration.

  4. 4

    Refresh cadence and anomaly handling

    State data latency and refresh time, and give anomalies an explanation path. Set threshold alerts for key metrics instead of requiring daily manual checks.

Recommended prompts

FAQ

How often should a dashboard refresh?

Match the decision cadence. Daily operations may need hourly refresh; weekly management reviews only need daily. Faster refresh raises maintenance cost and misread risk.

What if the boss wants more metrics?

Ask what decision it supports and what action follows an anomaly. If there is no action path, put it in a drill-down or appendix instead of the first screen.

Related skills