A dashboard that actually helps is one built around a few decisions a specific person makes regularly, showing only the numbers that inform those decisions, from data they trust. Most dashboards that get ignored fail on one of those three points: they try to show everything, they aren't designed for anyone in particular, or the numbers don't match what people see in their other systems. Fix those, and the chart styling matters far less than people expect.
Why so many dashboards get ignored
A common story: someone builds a dashboard with dozens of charts because every metric seemed worth including. Staff look at it a few times, can't find what they need quickly, and go back to checking the source systems directly. The dashboard becomes decoration.
The usual causes:
- No clear audience. One dashboard trying to serve the owner, the sales team and the warehouse at once.
- Too many metrics. When everything is shown, nothing stands out.
- Numbers people don't trust. If the dashboard total doesn't match Xero or MYOB, people stop using it the first time they notice.
- Stale data. A dashboard refreshed weekly isn't much use for daily decisions.
- No link to action. A number goes red and nobody knows who should do what about it.
Lesson 1: start with decisions, not data
Before choosing a single chart, write down who will use the dashboard and what decisions they make with it. For example:
- An operations manager deciding each morning which orders to prioritise.
- A finance manager deciding which customers to chase this week.
- A builder deciding whether a job needs attention before the next progress claim.
For each decision, ask what they need to know to make it. Those answers are your metrics. Anything that doesn't support a decision belongs in a report, not on the dashboard.
Lesson 2: fewer metrics, clearly ranked
A good dashboard usually fits on one screen without scrolling. A simple structure that works:
- Top row: the handful of headline numbers that tell the reader whether things are on track, such as cash on hand, overdue debtors, orders shipped or jobs over budget.
- Middle: trends that explain the headline numbers, such as this month against last month, or actual against budget.
- Bottom or drill-through: the detail for when someone needs to investigate, such as the list of overdue invoices or jobs over budget.
Each headline number should have context: a target, a comparison or a threshold. A number on its own doesn't tell anyone whether to act.
Lesson 3: the data has to be trusted
This is where most dashboard projects really succeed or fail, and it has little to do with design. If the data feeding the dashboard is incomplete, out of date or calculated differently from the accounts, people will stop relying on it.
Practical steps:
- Agree definitions. What counts as "revenue", "a completed job" or "overdue"? Write it down and use the same definition everywhere.
- Pull from the source systems. Connect directly to your accounting, CRM, inventory or job systems rather than relying on spreadsheet exports someone has to update.
- Reconcile to the accounts. Financial totals on the dashboard should match Xero or MYOB for the same period. Check this before launch and periodically after.
- Show when the data was last refreshed. A simple "updated at" note saves a lot of confusion.
If your data sits in several systems that don't talk to each other, joining it up is the first job. Our page on combining your business data into one dashboard covers that step.
Lesson 4: design for the reader
Once the content is right, a few design habits make dashboards easier to read:
- Use the right chart for the job. Lines for trends over time, bars for comparing categories, a single big number for a headline figure. Avoid pie charts with many slices and 3D effects.
- Use colour sparingly. Keep most of the dashboard neutral and use colour to highlight what needs attention, such as an overdue figure or a job over budget.
- Label clearly. Plain titles that say what the chart shows ("Overdue debtors by customer") rather than internal field names.
- Keep it consistent. Same colours for the same things across every page.
- Check it on the device people actually use. A dashboard used on a phone on site needs a different layout from one used on a large office screen.
Lesson 5: connect the dashboard to action
A dashboard is most useful when each warning has an owner and a next step. If overdue debtors go over a threshold, who follows up? If a job goes over budget, who reviews it? Some of this can be automated, such as alerts by email or tasks created in another system, but even a clear agreement about who watches which number makes a difference.
Choosing a tool
Power BI and Tableau are the two most common choices for Australian businesses. Power BI suits businesses already using Microsoft tools and is often the more affordable option. Tableau is strong for visual exploration of data. Our Power BI vs Tableau comparison goes through the differences. In practice, the tool matters less than getting the decisions, metrics and data right first. If you want help with that design and data work, see our data visualisation services.
Frequently asked questions
How many metrics should a dashboard have?
As few as the reader needs to make their decisions. Aim for a handful of headline numbers with supporting trends and detail behind them, and everything visible on one screen.
Why don't the numbers on our dashboard match our accounts?
Usually because of different definitions, timing differences between systems, or data exported and edited by hand. Connecting directly to the source systems and agreeing definitions fixes most mismatches.
Should each team have its own dashboard?
Generally yes. Different roles make different decisions, so a single dashboard for everyone tends to be too crowded for anyone. They can share the same underlying data.
How often should a dashboard refresh?
Match the refresh to the decision. Daily operational decisions need daily or more frequent data; monthly financial reviews can work with less frequent updates.
If your dashboards aren't being used, or you're planning your first one, book a free initial chat and we can talk through what your team actually needs to see.