Build a management dashboard people still use after the first month

Monday's meeting began with three definitions of monthly sales. Finance used settled cash, sales used submitted orders, and marketing used GA4 revenue. Every chart looked polished; each described something different. The failure was not visual design. The organisation had never agreed on the metric.

Start a dashboard with the recurring decision it should improve, not a blank canvas. If a number moves and no decision changes, it is probably decoration rather than a KPI.

Give every KPI an owner and a question

Ask which decision changes when the number moves. If there is no answer, the metric is probably decoration. Define its formula, source, refresh interval and owner.

Terms such as active customer or net revenue mean different things across teams. A concise data dictionary prevents contradictory reports and circular meetings.

Show less and explain more

Leaders need status, trend, distance from target and likely cause. A number without a target or comparison lacks context. Let people move from a warning to detail instead of placing every detail on the first screen.

Reserve colour for meaning. Red and green need documented thresholds and must remain distinguishable for people with colour-vision differences.

Trust before polish

Sales, advertising and support sources use different clocks and identifiers. Integration rules must explain matching, time zones and late-arriving corrections.

Every refresh needs quality checks and failure alerts. A dashboard silently showing yesterday’s incomplete data is more dangerous than no dashboard.

A sensible first release

• Covers three to seven recurring decisions.
• Every KPI has a definition and owner.
• Targets and time comparisons are explicit.
• Detail exists for diagnosis.
• Freshness and quality are visible.

Official resource: Google Looker Studio