Foldwren

Dashboard design basics for business tools

How to design a business dashboard by starting with the questions it must answer, using fewer charts, plain labels and clear next actions.

Most dashboards fail for the same reason: they show everything that could be measured instead of the few things someone needs to know. The result looks impressive in a demo and gets ignored by the second week.

A good dashboard answers a small number of questions at a glance and points to what needs doing. That is all it has to do.

Start with the questions, not the charts

Before anyone opens a design tool, write down the questions the person will have when they open this screen. Real questions, in their words.

Say you run a plumbing business with five vans. The office manager opening the dashboard at 7:30 am probably wants to know:

  1. Which jobs are on today, and is every one assigned?
  2. Is anyone running behind?
  3. Are there new enquiries waiting for a reply?
  4. Which quotes have been sitting unanswered for more than a week?
  5. Which invoices are overdue?

Notice what is missing. No "total revenue this financial year". No pie chart of job types. Those may be worth knowing once a quarter, but they are not what gets the day started.

Different people have different questions. The owner might care about cash flow and how booked out next month is. A technician wants only their own jobs. Trying to serve all three on one screen serves none of them. Either give each role its own view, or design for the person who will use it most.

A useful test for any item: if this number changed, would someone do something differently? If not, it is decoration.

Fewer charts, more answers

Charts are not automatically more useful than numbers. Often a single figure with some context beats any graph.

  • A big number with a comparison. "7 overdue invoices, up from 4 last week" tells the story in a line.
  • A short list. The five jobs on today, in time order, with status. For anything a person needs to act on item by item, a list beats a chart.
  • A line chart when the trend over time is the point, such as weekly bookings over the past three months.
  • A bar chart when comparing a handful of categories, such as enquiries by source.

Be wary of pie charts with more than three slices, gauges that look like car speedometers, and anything three dimensional. They take up room and are slow to read.

Put the important thing first

People scan a screen from the top, and on a phone they may never scroll. So order matters.

  • Top: whatever needs attention right now. Problems, exceptions, things waiting on this person.
  • Middle: today's activity and the key numbers.
  • Lower down: trends and background.

Use size and position to signal importance, and use colour sparingly. Save red for things that are truly wrong and amber for things at risk. If half the screen is red, people learn to ignore it. Never rely on colour alone either, since some users cannot tell red from green. Pair it with an icon or a word such as "Overdue".

Use plain labels

Dashboards attract jargon. Every label should make sense to a new staff member on their first day.

  • "Quotes waiting for a reply", not "Open pipeline".
  • "Jobs today", not "Daily work orders (active)".
  • "Paid this month", not "MTD receipts".

Three more labelling habits worth adopting:

  1. Say what period a number covers. "This week" or "Last 30 days", right beside the figure. An unlabelled number invites the wrong conclusion.
  2. Say when the data was last updated. If figures refresh overnight, tell people. Otherwise they will not trust a number that seems stale.
  3. Give comparison. A figure alone is hard to judge. Is 23 enquiries good? "23, compared with 18 last month" answers that.

Make every number lead somewhere

A dashboard that only reports is half finished. The point of knowing something is to act on it.

Each item should let the person get to the detail, or do the obvious next thing, in one tap.

  • "7 overdue invoices" opens the list of those seven, with a "Send reminder" button on each.
  • "2 jobs unassigned" opens those jobs with the roster beside them.
  • "3 new enquiries" opens the oldest one first.

If someone sees a problem on the dashboard and then has to go hunting through menus to deal with it, they will stop checking the dashboard and go straight to the menus.

Empty states matter too. When there are no overdue invoices, say so plainly: "Nothing overdue." A blank panel looks broken. A clear all good message is one of the nicest things a dashboard can tell you.

Review it after a month

Dashboards are easy to add to and hard to prune. Plan a review once people have used it for a few weeks.

  • Ask each regular user which parts they look at daily, and which they have never used.
  • Ask what they still go elsewhere to find out.
  • Remove anything nobody mentions.
  • Check it on the device people really use. A dashboard designed for a wide office monitor may be useless on a tablet in a van.

If you are commissioning a dashboard, bring your list of questions to the first meeting and ask the designer to show which element answers each one. Anything on the screen that does not map to a question should have to argue for its place.

Your order