Key takeaways
- Choose metrics that change a decision, not metrics that merely look interesting.
- Every KPI needs a definition, owner, source, and refresh cadence.
- A dashboard should show context: target, trend, and comparison.
- Too many KPIs hide the important ones; start with five to seven.
On this page
Start with the decision
Before choosing a chart, write down the decisions the dashboard should support. A sales leader may need to know which deals are slipping. A finance lead may need to know whether cash is tightening. An operations manager may need to see stock risk.
If a metric does not change what someone does, it probably does not belong on the first screen. This is the simplest test for whether a dashboard is useful.
Choose fewer metrics
A common mistake is putting every available number on one page. The result is a wall of data that nobody can scan. Start with five to seven metrics that cover the most important questions.
For an SMB, that might be revenue, gross margin, cash balance, overdue receivables, pipeline, and one operational metric such as stock risk or utilisation.
- One outcome metric per major function.
- One leading indicator for future performance.
- One risk metric that catches exceptions early.
Define every KPI
A KPI is not a number until it has a definition. Write down the formula, the source, the period, and any exclusions. For example, does revenue include tax? Are returns deducted? Is a month based on calendar days or a 4-4-5 retail calendar?
Definitions prevent the finance team and the sales team from arguing about whose number is correct. They also make the dashboard easier to maintain when someone new takes over.
Give every number context
A number by itself is hard to interpret. Add a target, a previous-period comparison, or a trend line. A revenue figure is more useful when you can see whether it is ahead of plan and whether margin is moving with it.
Use colour carefully. Red should mean attention is needed, not just that a number is below last month. Too much colour makes the important signals invisible.
Design for scanning
The best dashboards can be understood in a few seconds. Put the most important metrics at the top, group related numbers, and use consistent formats. Avoid tiny labels, unnecessary gridlines, and charts that require a legend to decode.
A simple table is often better than a complicated chart. The goal is not visual sophistication; the goal is a fast, accurate decision.
Review and maintain
A dashboard is a product, not a one-off project. Give it an owner, review it monthly, and remove metrics that are no longer used. Add new metrics only when a real decision requires them.
If the dashboard stops being reviewed, it will stop being trusted. A short monthly review is more valuable than another page of charts.
Frequently asked questions
How many KPIs should a dashboard have?+
Start with five to seven on the main view. Additional detail can live on secondary pages or in drill-downs.
Should every department have its own dashboard?+
Not necessarily. Start with one shared business view, then add role-specific views only when the audience and decisions are clearly different.
How often should a KPI dashboard refresh?+
Match the refresh to the decision. Daily operations may need daily data; monthly management reporting usually needs a monthly close, not a live feed.
Need help applying this?
Improve your bi dashboards & reporting.
Review the service scope or tell us what you are trying to improve. We will reply with a clear next step.
Free KPI definition templateRelated reading
What makes a dashboard useful?
A useful dashboard answers a specific question, uses numbers people trust, and leads to a decision.
Leading vs lagging KPIs: build a balanced dashboard
How to pair leading and lagging KPIs on a dashboard so teams can see outcomes and the signals that tend to precede them.