Almost every brand we meet already has a dashboard. Someone built it, there was a launch, people were trained on it.

Look at the usage and three people opened it last month, one of them by accident. The tool is rarely at fault. We tend to find the same four reasons.

01 / 04

It was built from whatever data was available

Most dashboards start with an audit of what can be connected. Whatever comes out of the systems easily ends up on the screen, arranged neatly and coloured well.

Then a planner opens it and still cannot tell whether to place the order. A controller cannot see why margin moved. Every number on the page is correct and none of them answer a question anyone was actually asking.

A report built from a decision looks different. It usually has fewer numbers on it, and one of them is the answer.

02 / 04

The first wrong number ends it

Trust in a report does not come back on its own.

Someone checks a figure against their own spreadsheet during a meeting and it does not match. Everyone in the room now knows the dashboard is wrong, and it makes no difference that the spreadsheet was the thing at fault. From that day the dashboard becomes something people verify before using, which costs more time than not having it at all.

This usually traces back to definitions nobody settled. Two teams counting revenue at different moments. Returns handled one way in finance and another in operations. The dashboard was accurate and the disagreement sat upstream of it.

03 / 04

Somebody has to remember to go and look

A dashboard waits. It only works for people who choose to open it, which in practice means the person who built it.

The planner is inside a buy sheet. The controller is in the close. The commercial lead is in a meeting that started ten minutes ago. Adding a browser tab to their week is a habit change, and habit changes lose to deadlines.

Reports that survive tend to arrive instead. In the pack before the meeting starts. In the sheet where the work already happens. In a message when a number crosses a line that matters.

04 / 04

It decays quietly

Someone renames a field upstream. A new sales channel launches and never gets added. A tax rule changes and the margin calculation is now slightly wrong.

None of this announces itself. The dashboard keeps loading and keeps looking healthy. The numbers drift, people use them for a while longer, and eventually somebody notices. Then you are back at the trust problem, permanently.

Ownership is what prevents it, and ownership is usually what nobody assigned. Someone inside the business has to be responsible for the pipeline, and they need to be able to read it and change it themselves.

We build reporting for businesses that already gave up on a dashboard once. What changes is the order of the work. Decide what the number is for. Settle the definitions once and write them into the pipeline. Deliver it where the work already happens. Leave someone able to maintain it.

The screen matters less than it used to anyway. When the definitions hold and the data sits in one place, someone can ask a question in plain language and get an answer with the workings attached. A dashboard was one way to reach the number, and it is no longer the only one.