Knowing What Went Wrong Is Not the Same as Knowing Why
By the time a monthly review reaches the problem, everyone in the room can already see it. Margin in one plant has slipped. A product line is costing more than the plan allowed. The number is on the screen, and nobody disputes it.
Then someone asks the only question that matters. Why did this happen. And the room goes quiet.
The report was very good at showing what changed. It has almost nothing to say about what caused it.
This is the quieter half of the decision gap. Even when a business catches a problem in time, it often cannot explain the problem in time. Seeing the number move and understanding what moved it are two different things, and most reviews deliver only the first.
The Reality
A number on a dashboard is the end of a long process, not the start of one. It is the result of thousands of transactions being added together, cleaned, and rolled up into a single figure a leader can read in a second. That summary is exactly what makes the number easy to see. It is also what makes the cause impossible to see.
The moment a figure looks wrong, the work runs in reverse. Someone has to break the number back apart. They pull the underlying transactions, compare them against last month, call the plant, check a purchase record, and slowly rebuild the story behind the movement. This reverse journey is manual. It lives in spreadsheets, in email threads, and in the memory of a few experienced people who know where to look.
Most organisations have quietly accepted this as the natural order of things. Someone always gets to the bottom of it eventually, usually a few days later. Because the answer arrives in the end, the days spent finding it are rarely counted as a cost. They are simply how long it takes to understand what happened.
The Business Impact
The real cost sits in the gap between seeing a problem and understanding it. During those days, the cause is very often still active.
Consider a margin drop that is eventually traced to a supplier who quietly changed the grade of a raw material. The number appeared at month end. The explanation arrived a week later. In between, the plant kept running on the same input, and several more weeks of production absorbed the same hidden cost before anyone could act on the reason.
The pattern repeats across the business. A rise in logistics cost turns out to be one route and one carrier, but until someone isolates it, the entire category looks broken and the wrong lever gets pulled. A shortfall in a region looks like a sales problem, so the whole team is pushed harder, when the real cause was a single delayed shipment that starved a few key accounts.
This is the deeper danger. When the cause is unclear, leaders are forced to act on the symptom. Costs get cut across the board when only one line was the issue. Pressure gets applied everywhere when the problem lived in one place. Decisions made from the wrong cause are not just slow. They are aimed at the wrong target.
Over time, the review meeting itself changes shape. Time meant for deciding what to do next is spent reconstructing what already happened and arguing about why. The meeting becomes a forum for explanation, not decision.
Why Traditional Approaches Do Not Solve It
The ERP holds the detail. The BI dashboard shows the summary. The gap sits in the space between them, and neither tool was built to cross it.
The ERP contains every transaction that could explain a change, but it will not tell you which ones matter unless a person already knows precisely what to ask. The dashboard shows the movement clearly, but it is built to display a result, not to investigate one. Excel can dig as deep as anyone wants, but only after a person decides where the digging should start.
Each of these tools answers its own question well. What is the number. How has it trended. What sits inside this account. None of them answers the question a leader actually has in the moment, which is what combination of factors caused this number to move, and which of them matters most. That question still depends on an experienced person manually connecting records across systems that do not speak to each other.
This is why adding another dashboard rarely helps. It does not add reasoning. It adds one more view of the same summary, and the cause stays buried in the detail underneath.
A Better Way to Think
The shift that matters is to treat the cause of a problem as something the business should surface, not something a person should reconstruct after the fact.
When a number moves, the explanation almost always already exists. The changed purchase record, the shifted order pattern, the single expensive route, the starved account. The cause is present in the data the moment the problem is. It is simply scattered across systems that were never designed to be read together.
This is where Enterprise Decision Intelligence changes the meeting. It does not replace the ERP or the dashboard. It connects the detail they already hold and traces a change back to the factors behind it, so a plant head or a CFO sees not only that margin moved but what moved it, in the same view and at the same time. The question of why gets answered before the meeting, rather than chased for a week after it.
The aim is not to take judgement away from leaders. It is to hand them the cause quickly enough that their judgement goes into the decision, instead of into the detective work.
Before your next review, it is worth putting a few questions to your leadership team:
- When a number surprises us, how long does it usually take to explain it, and who actually does that work?
- How much of our review time is spent reconstructing what happened, rather than deciding what to do about it?
- How often do we act on the visible symptom because the real cause did not become clear in time?
- If margin dropped in one plant this month, could we see the reason in the same report, or would we have to go and find it?
- How much of our root cause knowledge lives in the heads of a few experienced people and in old email threads?
- What would we decide differently if the cause of a problem reached us as quickly as the problem itself?
A problem you can name but cannot explain is not yet a problem you can solve. It is only one you have learned to live with.