Choose a small set of meaningful signals
Begin with questions people ask at the start of their day: what is overdue, what needs approval, what changed and where is help needed? Combine a measure with a useful route to the underlying record. A total without a date range or definition is difficult to interpret. Put time-sensitive exceptions ahead of decorative charts, and use labels that a new colleague can understand.
Review the dashboard as work changes
A widget that was useful during a rollout may become noise later. Ask users which parts lead to action and remove duplication. Check permissions so a convenient summary does not expose information the role should not see. Make refresh behaviour and filters clear, particularly where a view combines data with different update schedules. Demonstration figures should be identified as examples; real operational claims need the underlying evidence.