Two dashboards, two numbers: it is almost never a bug

The board opens two reports supposed to say the same thing. The figures differ by seven per cent. IT is blamed, an investigation is launched, and nobody finds a bug — because there is not one.

What is actually happening

Take an ordinary metric: monthly revenue. Two teams defined it, at two different times, for two different uses.

Financial control counts at invoice date, excluding tax, excluding credit notes from the prior year. Sales counts at signature date, including orders not yet invoiced, because that is what measures team performance.

Both definitions are correct. Both answer a legitimate question. They simply do not answer the same question, and giving both metrics an identical name creates the illusion that they should.

Why the technical fix fails

The usual reaction is to ask IT to "reconcile the figures". That is an impossible request: IT has no authority to decide what the company's revenue means. At best it can produce a reconciliation table explaining the gap, which occupies one person every month without ever fixing the problem.

The problem is a governance problem disguised as a technical one.

The fix: one definition per metric, written and arbitrated

Three steps, of which the second is the only hard one.

1. Inventory the existing definitions. For each key metric, list every variant in circulation, with the report each appears in and the actual calculation rule, extracted from the code rather than the documentation.

2. Have a business authority arbitrate. Financial control, usually. For each metric, one definition becomes the official one. The others do not disappear: they get renamed. "Revenue" and "signed revenue" are two distinct metrics, and simply naming them differently removes eighty per cent of the misunderstandings.

3. Write the definitions into the semantic layer. One implementation per metric, reused by every report. Any new definition must go through the same arbitration.

The point that blocks

The arbitration. Nobody wants to tell the sales director that their definition is not the official one. That is why this step must be sponsored by a general or financial management, never by IT, which has neither the standing nor the interest to decide.

Where that sponsorship does not exist, the most elegant technical project will change nothing: you will have a modern platform that still produces two different numbers.

The sign that it worked

The monthly reconciliation meeting disappears from the agenda. It is the only success indicator that matters, and it is verifiable.