A dashboard earns its place when it helps someone decide or act, not when it simply displays every metric available.
Start with the decision
Before choosing a chart, ask what decision the user needs to make. A programme manager, hospital administrator and service desk lead may use the same underlying data but need very different views.
Use operational definitions consistently
A metric is only useful when users agree on what it means. Status definitions, time windows, denominators and exception rules should be documented and applied consistently across source systems.
Show what requires attention
Operational dashboards should make pending work, unusual movement and exceptions easy to identify. Users should not have to inspect every number to discover where action is required.
Connect summary to detail
A high-level indicator becomes more useful when authorised users can move from the summary to the transactions or locations driving it. This supports investigation without overcrowding the primary view.
Review whether the dashboard changes behaviour
If a measure is never discussed or acted upon, it may not deserve prominent space. Dashboard design should evolve as operating priorities and user decisions change.