The dashboard was delivered and nobody opens it: the tool is not the problem

There is a situation that recurs often enough to be worth writing about. A company pays to have a consolidated reporting screen — usually called a dashboard — built for its sales or operations team. The handover goes smoothly and everyone finds it easy to read. Three months later, the access log shows that after the first week almost nobody opened it again.

Nobody filed a bug. Nobody complained. It simply stopped being used, and it usually takes until a year-end review before anyone asks why that investment produced nothing.

The first instinct usually runs one of two ways: blame the software — wrong platform, wrong layout — or blame staff for not being comfortable working with numbers. One figure shows that both are off target.

Same software, two usage rates three times apart

Surveys of business reporting software (business intelligence, or BI — the family of tools that build reports and charts from a company's existing data) consistently record a steady gap inside a single organisation: executives use it around 80%, while the average for employees is around 26%.

This is the same software, the same data source, the same interface — frequently the very same screen.

If the tool were the cause, those two numbers would sit close together, because both groups use the same thing. If skill were the cause, that is also hard to square: executives are rarely the most software-literate group in a company.

The difference lies elsewhere, and stated plainly it is fairly obvious: the leadership team has a recurring meeting where that number decides something, and someone has to answer if the number looks bad. A warehouse clerk has no such meeting.

Put differently, a reporting screen does not get opened because it is attractive, fast or comprehensive. It gets opened because a decision is waiting on it. With no decision waiting, no interface saves it.

Four conditions for a screen to be opened a second time

The first open always happens — out of curiosity, or because you are sitting in the handover session. The second is the one that has to be designed for in advance. Screens still alive after six months almost always have all four of the following:

• A recurring decision. Not "to keep an eye on things" but something specific: how much stock to order this week, whether the afternoon shift needs another person, which channel to stop spending on this month. A recurring decision creates a recurring reason to open the screen.
• A named person who is accountable. Not a department. If the decision belongs to "sales", usually nobody opens it, because work belonging to everyone belongs to no one.
• An action level for each number. Past how much, do what. A number with no action level is information to be aware of, and that does not need a dedicated screen.
• A fixed moment for opening it. Monday morning, the start-of-month review, or an alert that arrives on its own. A screen not attached to an existing meeting has to compete with everything else in the day for attention, and it always loses.

Miss one of the four and that screen dies — quietly. Nobody reports it, nobody asks for a fix. It just stops being opened, and it can take a very long time before anyone notices.

What is worth noting is that all four are matters of internal arrangement, not technical matters. None comes bundled with the software licence, and none is fixed by switching to a different reporting product.

"The numbers aren't trustworthy" is a common answer but rarely the root

Ask why a reporting screen goes unused and the most common answer is a lack of trust in the numbers. There is substance to this: roughly half of analytics reports are never used because the recipient does not trust the data source.

Data quality is a real problem, and we have written separately about how to monitor it. But there is a detail about sequence worth noticing.

You only discover that you do not trust a number at the moment you intend to act on it. Before that moment, every number looks fine. Which means losing trust is actually evidence that *someone tried to use it* — it happens on screens where somebody intended to act, and it never happens on screens nobody opened twice.

The practical consequence: cleaning up the data behind a screen nobody was going to use does not produce users. It produces a clean screen that still nobody opens. The right order is to identify the decision first, then invest in getting exactly the numbers that decision depends on right — at a level of effort matched to the damage of deciding wrongly.

Why everyone ends up back in a spreadsheet

Something happens almost without fail after a few months: people start exporting the data to a spreadsheet to work it out themselves. This is often read as users being stubborn. In fact it has a structural cause.

A reporting screen can only answer the questions its author anticipated. But real decisions tend to come from questions nobody anticipated: why this branch fell while that one did not, what the regulars who have not returned for two months have in common, which product line last month's variance came from. Questions like these rarely fit a pre-built screen.

When the question does not fit, users export to a spreadsheet — and that is a sensible choice, because a spreadsheet lets you ask a new question and a pre-built screen does not.

None of this makes reporting screens useless. It means this class of tool is good at tracking a known question over time and poor at answering a new one. Expecting it to do both is the source of most of the disappointment — and it is also why it pays to invest in fewer screens tied tightly to decisions rather than many screens built "just to have visibility".

In Vietnam there is one more layer: every system ships its own report

For companies working through digital transformation, the pattern above is amplified by something very familiar.

We have written about how digital transformation typically ends in five or six disconnected systems. For today's topic, the relevant part is that each of those systems arrives with its own built-in reports: the sales software has a revenue report, the warehouse software has a stock report, the accounting software has a receivables report.

The result is that a simple question like "how much did we make this month" produces three different numbers depending on which report you open. And here, not trusting the numbers is not a feeling — it is an entirely rational response to three figures that do not agree.

This needs saying plainly: it is not a reporting-tool problem. No tool fixes three systems understanding the word "revenue" three different ways — one counts revenue when the invoice is issued, another when the money arrives, a third includes orders not yet delivered. That is a matter of agreeing definitions and choosing one source as authoritative. Solve that and reporting becomes easy; skip it and each new report merely adds one more answer to an already contradictory list.

Where to start if you do it the other way round

• Start from the decision, not the data. Write down: every week, who has to decide what. If you cannot write that sentence, what you are building is a report to look at rather than a tool to decide with.
• Name the person and the opening moment before designing. One specific name, one specific time. These two decide a screen's fate more than any choice of colour or chart type.
• Require every number to carry an action level. Past how much, do what. This exercise usually removes half the planned charts, and that is a good outcome.
• Check the access log after thirty days and close what nobody opens. Almost every tool records who opened it and how often. Retire the dead ones rather than letting them dilute the list.

Conclusion

A reporting screen going unused is usually read as one of two stories: the wrong software was chosen, or staff are not comfortable with numbers. The 80% against 26% gap inside a single company shows both readings are off — same software, same data, a threefold difference.

What the leadership has and others lack is neither skill nor access. It is a recurring decision the number serves, and someone who has to answer if the number looks bad.

So a reporting screen is not yet a finished product. It is only half of one; the other half is a decision with an accountable owner, an action level and a fixed time to look at it. Build the first half without the second and what you get is an attractive screen that nobody opens.

If you have a delivered reporting screen that nobody uses and want to know which of the four conditions it is missing, get in touch to review a specific case, or see KonexForge's Data Analytics and Optimization Loop capabilities.