Why dashboards go unread
Most small companies build a dashboard once, look at it for a fortnight, and then stop. The usual diagnosis is discipline. The actual causes are structural.
Too many numbers. Thirty tiles means nobody knows which three matter, so the eye slides off all of them.
Numbers nobody owns. A metric with no name attached gets explained after the fact by whoever is in the room, which is not the same as being managed.
Lagging metrics only. Revenue closed last month is real and unchangeable. A dashboard made entirely of history is a scoreboard, and scoreboards get checked less as the game goes on.
No decision attached. If nothing different happens whether the number is up or down, checking it is a ritual.
The test for any metric
In the last three months, has anyone changed what they were doing because of this number? If not, remove it. Removing metrics is the cheapest way to make the remaining ones visible.
The sheet
Six to eight numbers, one page, same shape every week. Adapt the specifics; keep the structure.
| Area | Metric | Why it earns a place |
|---|---|---|
| Money | Revenue closed this week, and against target | The lagging truth. One number, not five |
| Money | Cash in the bank, and months of runway | The only number that ends companies |
| Pipeline | Deals with a dated next step, as a share of open deals | Leading. Predicts next month's revenue |
| Pipeline | New qualified opportunities this week | Leading. The earliest signal of a dry quarter |
| Customers | Accounts with more than one active user | Leading. The best retention predictor you have |
| Customers | Oldest unanswered enquiry, in hours | Service quality, and it hides in averages |
| Delivery | Things finished this week, by name | Makes completion visible, which nothing else does |
| Team | Anything red that was red last week too | Surfaces the thing everyone is quietly avoiding |
Four notes on why these specifically.
Cash and runway belong on a weekly sheet even when they are fine. Profitable companies fail on cash timing, and the number is only alarming if you meet it rarely.
Deals with a dated next step is a better weekly number than pipeline value, because value is easy to inflate and a dated next step is not. It is also the rule that makes a weekly pipeline review work at all.
Accounts with more than one active user is the retention metric most small teams do not track. Narrowing to a single user is the earliest churn signal, well before usage totals move, as covered in spotting a customer about to churn.
Oldest unanswered enquiry rather than average response time. Averages hide the two-week-old message, which is the one that costs you, for the reasons set out in setting up a shared inbox that doesn't drop enquiries.
Leading versus comforting
Every metric sheet accumulates numbers that feel good and predict nothing. They are worth naming, because they are seductive and they crowd out the useful ones.
| Comforting | What to track instead |
|---|---|
| Total pipeline value | Deals with a dated next step |
| Emails sent | Replies received |
| Total registered users | Users active this week |
| Average response time | Oldest unanswered message |
| Website visits | Enquiries from the website |
| Tasks completed | Things finished that a customer would notice |
| Meetings held | Decisions made |
The pattern is consistent: the comforting version measures activity you control, and the useful version measures response you do not. Activity metrics always look healthy, because effort is easy to produce.
Using it in the week
The sheet is worthless without a slot. Attach it to something that already happens.
One person updates it before the weekly review
Fifteen minutes, same time each week. Automate the collection where you can so the update never has to be skipped.
If updating it takes an hour, it will not survive a busy fortnight. That is a data problem, not a discipline problem.
15 minutes, before the meetingFive minutes in the review, on exceptions only
Not a walk through every number. Only what moved unexpectedly and what anyone plans to do about it.
This fits directly into the review slot in a [weekly operating rhythm](/blog/weekly-operating-rhythm) rather than needing a meeting of its own.
5 minutes, exceptions onlyAnything red twice gets a decision, not a discussion
An owner, an action, and a date. The same number being red for four weeks with sympathetic conversation each time is how a metric sheet loses credibility.
Two strikes, then actReview the metrics themselves quarterly
Which of these changed a decision this quarter? Remove the ones that did not, and consider whether the gap you keep guessing about deserves a number.
Sheets grow on their own. Nobody ever schedules the pruning, which is why it has to be a fixed item.
QuarterlyRemove more than you add
One last point about tooling. The reason most small teams stop updating a metric sheet is that the numbers live in four systems and assembling them by hand takes an hour nobody has. That is worth measuring before you solve it: a time audit usually shows the reporting itself is one of the larger admin costs in the week, and the fix is to reduce the number of places the same fact is stored rather than to try harder at the assembly.
Frequently asked questions
- How many metrics should a small team track weekly?
- Six to eight. Beyond that nobody reads all of them, and the ones that matter get lost among the ones that do not. Additional detail belongs in a monthly or quarterly review.
- What is the difference between a leading and a lagging metric?
- A lagging metric reports what already happened, such as revenue closed. A leading metric predicts it, such as meetings booked. You need both, but only leading metrics let you change the outcome while there is still time.
- Should metrics be automated?
- Collection yes, interpretation no. Automating the gathering removes the excuse for skipping the review; automating the judgement produces a dashboard nobody reads because nobody feels responsible for it.
- What makes a metric worth keeping?
- Someone changes what they do because of it. If a number has never altered a decision in three months, it is a report rather than a measure, and removing it makes the remaining ones easier to see.
- Who should own each metric?
- One named person per number, responsible for knowing why it moved rather than for the number being good. Metrics owned by the team are owned by nobody and get explained by whoever happens to be in the room.