Every month, a report goes out. It has charts, color-coded tables and dozens of numbers. It took someone hours to put together. And most months, it's opened for about thirty seconds before everyone goes back to making decisions the way they always have — on instinct, a few numbers they check themselves, and whatever went wrong last week.
If that sounds familiar, the problem usually isn't a lack of data. It's too much of it, organized around what's easy to measure rather than what you need to decide.
How dashboards get bloated
Nobody sets out to build a forty-metric dashboard. It happens gradually.
- Software defaults. Accounting, ecommerce and marketing platforms come with built-in reports. It's easy to pull all of them in because they're already there.
- "Might as well track it." Every new question adds a new chart. Nothing ever gets removed.
- Reporting for reporting's sake. Metrics get added because they seem like something a well-run business should watch, not because anyone uses them.
- No clear owner. When no one is responsible for a number, no one notices that it hasn't mattered in a year.
The result is a dashboard that's comprehensive and nearly useless. When everything is highlighted, nothing is.
The one test that matters
There's a simple way to decide whether a metric belongs on your dashboard:
If a metric has never once changed a decision you made, it's decoration.
Go through your current report and ask that of each number. When did this last cause you to do something differently — hire, cut, reprice, reorder, call a customer, move budget? If you can't remember, it's a candidate to remove.
This isn't about tracking less for its own sake. Plenty of data is worth keeping in the background, available when a question comes up. The dashboard is different. It's the short list of numbers you look at on purpose, on a schedule, to decide what to do next.
Start from the decisions, not the data
The better way to build a dashboard is to work backward from the decisions you actually make.
Step 1: List your recurring decisions. Think in terms of rhythm. What do you decide every week? Every month? Every quarter? For example:
- Weekly: how much inventory to reorder, how to schedule staff, where to put this week's ad spend
- Monthly: whether spending is on track, which products or services need attention, whether to adjust pricing or promotions
- Quarterly: whether to hire, whether to invest in a new initiative, whether the plan is working
Step 2: For each decision, name the number that would inform it. Reordering inventory needs weeks of stock on hand and recent sales pace. Ad spend needs cost to acquire a customer against the margin that customer brings in. Hiring needs revenue per employee, workload trends and cash runway.
Step 3: Define each number precisely. "Margin" means different things to different people. Write down exactly how each metric is calculated and where the data comes from, so the number means the same thing every month.
Step 4: Match the number to the rhythm. Weekly decisions need weekly numbers. Putting a quarterly metric on a weekly report only creates noise.
What you'll usually find is that a business needs somewhere between six and twelve numbers on its main dashboard. Everything else can live one click deeper.
Give every number a job.
- 01
Decision
What do you need to decide?
- 02
Metric
Which number informs it?
- 03
Definition
How is it calculated?
- 04
Rhythm
When do you need to see it?
How much should we reorder?
Weeks of stock on hand + recent sales pace
Review weekly, before the reorder decision.
Keep the main dashboard focused on decisions. Supporting detail can live one level deeper.
Leading and lagging: know which you're looking at
A useful dashboard mixes two kinds of measures.
Lagging measures report results after they've happened: revenue, profit, cash in the bank, customer churn. They tell you how you did. By the time they move, the cause is already in the past.
Leading measures show what's likely to happen next: sales pipeline, website conversion rate, repeat-order rate, backlog, average days to collect from customers. They give you time to act.
Most small-business reporting is almost entirely lagging, which is why problems tend to show up as surprises. Adding a few leading measures — one or two per important outcome — is often the single biggest improvement you can make.
An example: from cluttered to useful
Consider a growing multi-location service business. (Illustrative.) Its monthly report covered forty-plus metrics: revenue by location and by service line, website sessions, social followers, email open rates, a dozen expense categories, average ticket size, reviews, headcount, and more.
The owner's recurring decisions came down to a handful of questions: Is each location pulling its weight? Are we staffed correctly for demand? Is marketing spend bringing in profitable customers? Do we have the cash to invest in what's next?
Working backward from those questions, the main dashboard became one screen:
| Decision | Metric | Type |
|---|---|---|
| Is each location performing? | Contribution margin by location | Lagging |
| Are we staffed for demand? | Booked hours vs. available hours, next 4 weeks | Leading |
| Is labor cost under control? | Labor cost as % of revenue | Lagging |
| Is marketing working? | Cost per new customer vs. first-90-day margin | Leading |
| Are customers coming back? | Repeat-visit rate | Leading |
| Is cash healthy? | Cash on hand and weeks of runway | Lagging |
| Are we getting paid on time? | Average days to collect | Leading |
Seven numbers. Website sessions, followers and open rates didn't disappear — they moved to a marketing detail page, where they're useful for the person running campaigns. But they no longer compete for the owner's attention.
The practical difference was immediate. Monthly reviews got shorter and more focused, and conversations shifted from "what does this chart mean?" to "what are we going to do about it?"
What happens to everything you cut
Removing a metric from the main dashboard doesn't mean deleting the data. It means moving it to where it's useful. Detail pages for marketing, operations or finance can hold the supporting numbers for the people who manage those areas day to day. When a headline number moves, those pages help explain why.
The distinction is simple: the main dashboard is for deciding, detail pages are for diagnosing. Keeping those two jobs separate is what lets the main view stay short.
Keeping a dashboard useful
A good dashboard doesn't stay good on its own. A few habits keep it that way:
- Give every number an owner. One person is responsible for each metric: explaining it when it moves and proposing what to do.
- Set a review rhythm and keep it. A standing monthly review, with the dashboard as the agenda, does more than any feature.
- Set expectations, not just targets. Know what normal looks like for each number, so real changes stand out.
- Prune regularly. Once or twice a year, apply the test again. Remove what hasn't driven a decision. Add what's missing.
- Keep it on one screen. If it takes scrolling to see the main dashboard, it's too long.
Fewer numbers, better decisions
The goal of reporting isn't to know everything. It's to know the few things that tell you what to do next, early enough to do it. A dashboard built that way gets opened, gets discussed and actually changes how the business runs.
If your reporting takes a lot of effort and still doesn't answer the questions you care about, it's worth rebuilding it around the decisions instead.