Almost every business software project produces a dashboard. Almost every dashboard is opened enthusiastically for two weeks and then not at all.
The usual diagnosis is that people need training, or that the dashboard needs more data. Both are wrong, and adding more data reliably makes it worse.
Dashboards fail because they answer questions nobody was asking. A screen full of accurate, well-presented numbers that do not change what anyone does is a screen with no reason to be opened. The ones that survive share a single property: every element on them is attached to a decision somebody actually makes.
The test each number should pass
Before a metric appears on a dashboard, it should survive three questions.
Who looks at this, and when? Not "management" — a specific person, at a specific point in their day or week. A number without an owner and a moment is decoration.
What would they do differently? If the figure is high, what happens? If it is low, what happens? If the honest answer is "nothing, it's just useful to know", it does not belong on an operational dashboard.
How quickly do they need it? A figure reviewed monthly does not belong on a screen checked daily. Different cadences want different surfaces.
Most metrics fail the second question. That is the filter that does the work.
Awareness and action are different screens
The most common design error is mixing two purposes.
Awareness answers how are we doing — revenue, volume, trend. It is reviewed periodically, it is interesting, and it rarely triggers an immediate act.
Action answers what needs attention now — stock below reorder, invoices past due, variance beyond threshold, an outlet that has not closed its day.
They belong on different screens because they are consumed differently. Awareness is reviewed on a cadence. Action should be checked whenever there might be something to do — and if action items are buried among charts, they are missed.
The practical consequence: an operational dashboard should mostly be a list of exceptions, not a wall of charts. If nothing needs attention, it should say so and be short.
Why more data makes it worse
When a dashboard is not being used, the instinct is to add to it. This is exactly backwards.
Every additional element costs attention and dilutes the signal. A screen with six numbers where two matter is a screen where the two get missed. A screen with thirty is not opened at all.
Our position is focused screens, not dashboards — every screen shows what a decision needs and nothing else. Decorative analytics cost attention and return nothing. It is one of the three principles that decide what we ship, described in how Truffaire builds software.
The discipline is subtraction. A useful review question is not "what else should we show" but "what could we remove without changing any decision".
What belongs on an operational screen
For most operations, a short list:
- Exceptions requiring action today — with enough context to act, not just a count
- Yesterday's close — did the day settle, and was there variance
- Anything below a threshold — stock, cash position, margin
- Anything overdue — receivables, deliveries, follow-ups
- A single trend line for the one number the business steers by
Notice what is absent: breakdowns by every dimension, comparisons nobody requested, and charts that exist because the data was available.
Exceptions need context, not just counts
"14 items below reorder level" is a number. It requires the reader to go and find out which, how far below, and whether it matters.
"14 items below reorder — 3 are fast-moving and will stock out this week" is a decision. The work of interpretation has been done by the system rather than deferred to the person.
That difference decides whether a dashboard saves time or creates it.
Where dashboards get abandoned
Stale data. If the numbers are yesterday's and the decision is today's, the screen is worse than useless — it is confidently wrong. This is the strongest argument for a shared record: figures derived from one source are current by construction rather than by a sync schedule. It is the architecture in what a business operating system actually is.
Numbers that disagree with reality. One instance of a dashboard contradicting what someone can see with their own eyes destroys trust in the whole screen, permanently and reasonably.
Requiring interpretation. If reading it needs a mental calculation, it will be skipped when busy.
Built for the buyer, not the user. Dashboards specified by an owner and used by a manager frequently answer the owner's questions. The manager opens it twice.
No mobile reality. Most operational checking happens on a phone, often away from a desk. A dashboard that only works on a large screen is checked far less than one designed for the device it is actually opened on.
What we have seen
Dashboards appear in most of the ten systems we have delivered. The pattern is consistent: what gets used long-term is narrower than what was originally requested.
Clients typically ask for comprehensive visibility. Six months in, the screens still open daily are the exception lists — what needs attention, what did not close, what is below threshold. The comprehensive analytics are reviewed occasionally, if at all, and usually by one person.
The other finding is that the most valuable screen in an operation is frequently the daily close: did yesterday settle, and if not, by how much. It is unglamorous, it is one number with a variance, and it is checked every morning — because it is attached to something the person is accountable for.
That is the whole principle. Attachment to accountability is what makes a number get looked at.
Frequently asked questions
How many metrics should a dashboard have?
Fewer than you think. For a daily operational screen, five to seven elements is generally the ceiling before attention disperses. If more seems necessary, it is usually two screens for two audiences.
Should everyone see the same dashboard?
No. A counter supervisor, an outlet manager and an owner make different decisions and need different screens. One shared dashboard is a compromise that serves nobody particularly well.
Real-time or periodic?
Match the decision. Stock and daily close benefit from being current. Monthly trends do not need real-time and updating them constantly adds noise. Real-time everything is a cost with no corresponding benefit.
What about alerts instead of dashboards?
Often better for the action category — if something needs attention, pushing it is more reliable than hoping someone checks. The risk is volume: alerts that fire too often get muted, and then the important one is muted too.
How do we know if ours is working?
Look at whether it is opened, and by whom. If a screen is not being checked, do not add to it — remove from it, or ask the person what they actually needed to know.
Where to start
Take your existing dashboard and, for each element, name the person who acts on it and what they do differently based on it. Remove anything that fails.
What remains is usually a short list of exceptions and one or two trends. That is the dashboard people will actually open — and it will be more useful than the comprehensive one it replaces.
If nothing survives the filter, the honest conclusion is that the screen was built because dashboards are expected, not because a decision needed support. That is worth knowing before investing further in it.
SPEXA treats dashboards as exception surfaces first. If you want a read on which of your numbers are actually load-bearing, get in touch.