Why two departments never agree on the number

The number is not the problem. The word is.

Take the word revenue. To a sales director it usually means what was signed this month, because that is what the team is measured on. To finance it means what was invoiced, or what was recognised under the accounting rules, or what was collected, depending on who is asking and why. To the marketing manager it is the value of the deals that came from a campaign, attributed on whatever rule the campaign tool applies.

Every one of those people can pull a report that supports their figure. None of them is wrong. They are answering different questions with the same word, and the systems they use were each set up by a different supplier who defined the word their own way.

The same thing happens to customer (a person, a company, a billing account, or an email address?), to lead (a form fill, a phone call, a qualified conversation?), to margin (before or after the cost of the sales team, the licence fees, the returns?) and to active (logged in this month, paid this month, or simply not cancelled?). Ask three managers to define any of these and you will get three careful, reasonable answers that do not match.

Why the software never fixes it

Most companies respond to the mismatch by buying something: a new reporting tool, a connector between two systems, a bigger licence. It does not help, because the disagreement was never in the software. Every system is faithfully reporting the definition it was given. Connecting two of them just puts two definitions side by side on one screen, where they disagree faster.

Nor does the spreadsheet fix it, although the spreadsheet is where most businesses end up. Somebody in finance exports from each system, adjusts the figures until they reconcile, and produces a pack that everyone accepts because nobody else knows how it was built. When that person is on leave, the number moves. When they leave the company, it disappears.

What actually stops it

Someone has to write the definition down once, in a place every report reads from. Not in a policy document, which nobody opens, but in the layer that sits between the source systems and the dashboards, so that when the board pack says revenue and the sales dashboard says revenue, they are both computing the same thing from the same rows.

In our work that layer is the first thing we build, before any dashboard, and we call it the ontology: a plain list of the business's own terms, each with one agreed definition, each mapped to where the data for it actually lives. It is a conversation as much as a technical job. The sales director and the finance director sit in the same room, argue about what revenue means for an afternoon, and leave with an answer that is written into the system rather than into someone's head.

Once that exists, the argument in the Monday meeting goes away, not because anyone lost it but because there is nothing left to argue about. The interesting conversation, what to do about the number, finally gets the twenty minutes.

Three questions to ask this week

Pick the figure your leadership team looks at most often. Then ask the people who produce it these three questions. First: which system does this come from, and does anything get adjusted by hand on the way? Second: if I asked a different department for the same figure, would I get the same answer? Third: if the person who builds this report were away for a month, who else could produce it?

If any of the three makes the room go quiet, the gap is not in your software. It is in the definitions, and it is fixable in weeks rather than years.