What We Learned Building Dashboards People Actually Use

Almost every project we start includes a request for “a dashboard”. Almost every client also has an old dashboard nobody opens. The difference between the two is rarely the charts. It’s whether the screen answers a question someone has every day.

Start with the question, not the data

Before we draw anything, we ask each person who will use the dashboard: what do you need to know first thing on a Monday? The answers are usually specific. “Which bookings haven’t been ticketed?” “Which students haven’t logged in this week?” “Which projects are slipping?”

A good dashboard makes someone do something. If nobody acts on a number, it doesn’t belong on the first screen.

Lessons we keep relearning

• Fewer numbers, more context. A figure on its own means little. Compared with last week, or with a target, it tells a story.
• Make every number clickable. If a tile says twelve overdue tasks, one click should show those twelve tasks.
• Show what needs attention first. Put problems at the top and the good news below.
• Be honest about freshness. Say when the data was last updated, especially if it isn’t live.

Design for the busiest person

The person who most needs the dashboard is often the one with the least time. We test layouts by asking them to find an answer in under ten seconds. If they can’t, we simplify.

Measure whether it’s used

We track which tiles get clicked. After a month, anything nobody opens moves to a report page. Dashboards should get simpler over time, not busier.