The dashboard is live. The project is finished. Then Monday morning arrives, and someone exports the numbers into Excel.
They adjust a few rows, add information from another system and email the spreadsheet before the weekly meeting. A colleague asks which version to use. Someone else has a different total.
If this sounds familiar, the useful question is what the spreadsheet is doing that the dashboard still cannot. The answer may reveal the business problem the reporting project has left unresolved.
The meeting starts with an argument about the numbers
Imagine a retailer preparing for its weekly trading meeting. This is a hypothetical example, not a DataDive client case study.
Sales brings revenue figures that look encouraging. Finance brings a margin report that tells a less comfortable story. Operations points to orders that have been taken but not yet delivered.
These reports describe different parts of the business. The difficulty begins when everyone expects them to answer the same question: how are we doing, and what should we change?
Does the sales figure include returns? Have discounts been allowed for? Are the costs current? Which orders count towards this week’s result?
The meeting becomes a search for an explanation. Decisions about pricing, promotions and stock wait while someone promises to check the spreadsheet and come back.
The spreadsheet is filling a gap
Before asking the team to stop using Excel, watch what they do after exporting the report. Each adjustment tells you something.
Perhaps they remove cancelled orders, correct a product category, add the latest supplier costs or separate a promotion from ordinary sales. Perhaps they simply need to put two reports beside each other to answer a question that neither report answers alone.
Some spreadsheet work is useful exploration. The concern is the repeated workaround that has become part of producing the supposedly finished report.
If the same adjustments are needed every week, the dashboard has left part of the reporting job with the person preparing the meeting.
The hidden cost is work that never disappears
The export itself may be quick. Checking it, explaining it and resolving competing versions take more effort. That work repeats whenever the question comes up.
There is also dependence on the person who knows which rows to change and why. When they are away, a colleague may reproduce the spreadsheet without understanding its assumptions, or the decision may wait for their return.
Meanwhile, the business still needs to act. A pricing change can be delayed while margin is checked. A stock decision can wait while sales are matched to outstanding orders. The practical cost of reporting includes what happens while people are waiting for an answer they trust.
Start with the decision the report should support
Choose one recurring decision. For the retailer, it might be deciding which product categories need a pricing or promotion review at the weekly trading meeting.
Bring together the people who make that decision and the person who currently prepares the spreadsheet. Agree what number they need, what it includes and when it needs to be ready.
Then look at the adjustments being made today. Which reflect agreed business rules? Which correct a recurring problem? Which depend on knowledge that only one person holds?
Finally, ask what information turns the number into an action. A manager who sees falling margin needs to understand whether discounts, changing costs or returns are behind it. Sending them away to build another spreadsheet leaves the important part of the question unanswered.
The aim is a report that helps them see the reason for the change and decide what to investigate or do next.
Judge the improvement by what changes in the working week
After improving the report, return to the same meeting and the same decision. Ask:
- Which manual adjustments no longer need to be made?
- Can the manager answer the normal follow-up questions without asking someone to prepare another file?
- Can the team act earlier because it spends less time checking the result?
- Can someone else use and explain the report when its usual owner is away?
These questions connect the reporting investment to the work it was meant to improve. A dashboard being opened is a start. A repeated task disappearing, or a decision becoming easier, is stronger evidence of its value.
One report. One decision. One workaround.
Our previous article on modern ELT looked at the architecture behind reporting. This is the next step: making those foundations useful in everyday business decisions.
You do not need to begin with another full reporting rebuild. Choose one report, identify the decision it supports and follow one recurring spreadsheet workaround to its cause. That gives the next improvement a clear purpose.
If your dashboard is live but your team still prepares the real answer in Excel, DataDive can help review the gap between the report and the decision. Explore our reporting and dashboard services, or tell us which report still needs a spreadsheet before anyone can act.