Designing a dashboard around decisions

A dashboard becomes useful when it helps someone choose a next action. More charts rarely solve a problem of unclear priorities.

Start with the operator’s question

Ask what a person needs to decide during a typical session. Record the information they check, the comparisons they make and what happens after they notice a problem. Use those observations to define the overview rather than beginning with available data sources.

Give exceptions a clear path

An unusual value needs context: how far it sits outside a normal range, who owns it and which action is appropriate. Place that information together, and keep the detailed evidence within reach. Avoid making colour the only way to distinguish urgency.

Review with realistic variation

Test the layout with a quiet day, a busy day and a missing-data state. A useful dashboard remains understandable when every chart is not neatly populated. Document what each metric means and when it was last updated.

A useful first exercise is to write the three questions an operator asks at the start of a shift, then place the relevant information beside each one. Any chart without a clear role can move to a secondary view.