It is one of the most common questions a leadership team cannot answer quickly, and the reason is almost never that the numbers are wrong.

Consider an illustrative professional services firm. Over twelve months: revenue up 14%, headcount up 8%, delivered output up 6%, and margin down 2.1 points. Every one of those figures is correct. Finance can defend the margin number, HR can defend the headcount number, and Delivery can defend the output number.

Nobody can explain the relationship between them.

The arithmetic hides in the gaps

Margin moved because of some combination of at least four things:

  • Cost per unit of capacity rose — salary increases, benefits load, a shift in seniority mix
  • Capacity was used differently — utilization fell, or non-billable time rose
  • What was sold changed — a shift toward lower-margin work, or discounting
  • Delivery consumed more than it was priced to consume — scope creep, rework, longer cycles

Each of those lives in a different system, owned by a different function, measured on a different calendar. Finance holds cost in the ERP. Workforce holds capacity and rates in the HRIS. Sales holds what was promised, in the CRM. Delivery holds what actually happened, often in a project system and a spreadsheet.

To attribute the 2.1 points you have to connect all four to the same projects, the same periods, and the same definition of a person.

Why the monthly pack cannot answer it

A monthly reporting pack is organized by function because that is how the systems are organized. It answers "what did Finance see" and "what did Delivery see." It does not answer "which of those explains the other."

So the question gets escalated, an analyst is pulled off other work, extracts are assembled by hand, and two weeks later a number arrives that somebody disputes because their system says something different.

That is not a reporting failure. It is a structural one: the question crosses boundaries that the reporting was never built to cross.

What answering it actually requires

Four things, in order:

  1. A shared definition of the entities — what is a project, a person, a customer, a period. These usually differ across systems in ways nobody has documented.
  2. Join paths that hold across history. A reorganization two years ago that renamed cost centers will silently break any comparison spanning it.
  3. A decomposition method agreed in advance — how much of the movement is attributed to rate, to mix, to utilization, to delivery. Without agreement up front, the answer becomes a negotiation.
  4. A named owner for each metric, so that when someone disputes the number there is a person who decides rather than a meeting that re-litigates.

The test

If your organization can produce a margin bridge — a statement that says rate explains 0.8 points, mix explains 0.6, utilization explains 0.5, and 0.2 is unexplained — and every function accepts it, you have connected intelligence.

If the answer takes two weeks and gets argued about, you have accurate reporting and no explanation.

Those are different problems with different solutions, and only one of them is fixed by better dashboards.

Understanding which questions your organization can and cannot answer today is the work of a 360° Enterprise Intelligence Blueprint.