I've been asked to "build a dashboard" more times than I can count. The request almost always means well: the team wants to see how the business is doing without asking someone to pull numbers. But the result is often a page with thirty charts that gets opened twice and then forgotten.
The dashboards that survive aren't the most complete ones. They're the ones built around a meeting.
Start from the meeting, not the data
Ask who will open the dashboard, when, and what they'll decide afterwards. A Monday trading meeting needs something different from a monthly board update, and both need something different from a marketer checking a campaign.
For a weekly trading meeting, the questions are usually simple. Are we on track this week? What changed since last week? Is anything broken? A good dashboard answers those three questions in the first screen, before anyone scrolls.
Five rules I use
1
Put the four or five numbers that matter at the top
Revenue, orders, conversion rate, new customers: whatever the meeting actually discusses. Everything else goes below, or on another page.
2
Always show a comparison
A number on its own means nothing. Show it next to last week, the same week last year, or the target. The comparison is what turns a number into a conversation.
3
Use the same definitions everywhere
If "revenue" includes tax on one page and excludes it on another, people stop trusting all of it. Write the definitions down and link to them from the dashboard.
4
Make broken data obvious
A sudden drop to zero is usually a tracking problem, not a business one. Flag days where data looks incomplete, so nobody makes a decision on a broken number.
5
Remove a chart for every one you add
Dashboards grow until nobody can read them. A simple rule keeps them useful: if a new chart earns its place, an old one has to go.
Explore separately
The weekly dashboard isn't where you investigate. When a number looks odd, the right move is a separate, focused piece of analysis that answers one question and then goes away.
Keeping the two apart is what keeps the dashboard fast to read. It also stops the slow creep where every one-off question becomes a permanent chart that nobody remembers asking for.
Test it on a phone
Many people check the Monday numbers on their phone before the meeting. If the top of your dashboard doesn't read well on a small screen, it isn't doing its main job.
Signs your dashboard is working
People quote it in meetings. Questions shift from "what happened?" to "why did it happen?". And when the data breaks, someone notices within a day, because they actually look at it. That's the whole goal: a page that's part of how the team works, not a project that was finished once.
