A dashboard should help a defined role make a decision. Select metrics after identifying the questions, time horizon and available actions.
Identify the usage moment
For a fictional field-operations product, a morning dispatcher needs urgent jobs without an assigned technician. A monthly executive review needs workload and delay trends. One screen mixing both can make each task harder.
| Question | Useful presentation |
|---|---|
| What needs attention? | Prioritised list with an action |
| What is changing? | Trend over comparable periods |
| Why this total? | Access to contributing records |
| Can I trust it? | Visible definition and freshness |
Expose data limitations
Distinguish zero, unavailable data and calculation in progress. Show filter scope and relevant update time. An attractive chart can mislead when the population or period changes without explanation. International reporting may also require an explicit time-zone convention.
How many metrics belong on the screen?
Enough to support its decisions, not enough to fill a layout. Test a realistic question and observe whether the user reaches an answer and next action. Move detail into a dedicated view when it does not support the immediate task. A clear table may serve the decision better than a complex chart.
Currency totals require an explicit policy
If a dashboard aggregates transactions in different currencies, explain whether it groups them or converts them using a defined method. Do not let an English locale imply a single currency. A total without that context can support the wrong operational decision.
From this guide to your project
Product ↗
The experience connects your promise to the job your user needs to get done. We design that journey before adding more screens.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗