Design business dashboards around decisions

If a number on your dashboard would not change what anyone does, it does not belong there. It is a useful starting point for deciding what the main screen needs.

Crowded dashboards are rarely built carelessly. They accumulate. Each addition seems reasonable, and nothing is ever removed, until the display is complete and useless at the same time.

Start from the decision

For each panel, ask what decision it informs, who makes that decision, and how often. If you cannot answer all three, the panel is decoration.

Working backwards from decisions usually produces a short list. That brevity is the point. The right amount depends on the task, the audience and how the view is organised.

Build role-specific views

An owner, a supervisor and a coordinator need different things. A shared overview may help, but each role also needs access to its own tasks and decisions.

• The person doing the work needs today's queue and anything blocked.
• The person running the team needs where work is stalling and where capacity is short.
• The person running the business needs direction of travel and the few figures that signal trouble early.

Separate views are more work to design and much less work to read.

Show exceptions, not totals

Totals provide context, while exceptions can point towards a specific action. Exceptions are where attention belongs: items overdue, jobs without an owner, records missing required information, anything stalled longer than it should be.

Pair each exception with an action. A list you can click into and resolve is a tool. A count you can only look at is a worry.

An exception list should become quieter as issues are resolved; stable totals and trends may still be useful alongside it.

Leading and lagging

Lagging indicators describe what already happened. They help with accountability and reviewing completed work, even when the immediate opportunity to intervene has passed.

Leading indicators are the earlier signals: enquiries this week, jobs entering the pipeline, response times, capacity booked ahead. They can support earlier intervention, but their relationship with later outcomes should be checked rather than assumed.

The numbers are only as good as the record

A dashboard is a view over a source of truth. If the underlying records are incomplete, entered inconsistently or updated late, the display will present that unreliability with a confident chart and people will stop trusting it.

When a figure looks wrong, check the source records, calculation and display before deciding where the problem sits.

A short pruning exercise

1. List every panel currently displayed.
2. For each one, name the decision it changes and the person who makes it.
3. Delete anything without an answer.
4. Of what remains, mark which are leading and which are lagging.
5. Replace at least one total with an actionable exception list.
6. Review again in three months and delete whatever nobody has used.

Keep a record of what was removed and ask users whether they can still complete their tasks. Restore or redesign a view if useful context has been lost.

A dependable view starts with well-defined operational data. Explore business systems for the records and workflows behind the dashboard.