Advertisement /206696744/dsx/crmroute_top_over_banner · 970×90
CRM Route
Advertisement /206696744/dsx/crmroute_top_below_banner · 728×90

One Metric, One Definition, One Owner

When two dashboards disagree about revenue, the problem isn't the tooling. It's that nobody was ever made responsible for deciding what revenue means.

One Metric, One Definition, One Owner

The most common failure in business intelligence is not a slow query or an ugly chart. It is two credible people bringing two different numbers for the same thing to the same meeting, and the meeting becoming about the discrepancy instead of the decision.

Why the numbers differ

They differ for mundane, discoverable reasons, and it is almost always one of these:

• Different date basis — order date, ship date, invoice date, recognition date.

• Different treatment of cancellations, refunds and credit notes.

• Different currency conversion — transaction rate, month-end rate, or budget rate.

• Different filters on test accounts, internal orders and staff purchases.

• Different timezone boundaries for what counts as 'yesterday'.

None of these is a bug. Each is a defensible choice made independently by two analysts who were never told which choice was the house standard, because there wasn't one.

The three rules

Every metric that appears in a management conversation needs all three of these, and the third is the one organisations skip.

Advertisement /206696744/dsx/crmroute_scroll_in_articles · 300×250

• One definition, written in business language, with the edge cases stated explicitly.

• One implementation, in a shared modelling layer that every dashboard reads from.

• One owner — a named person who decides when the definition changes.

A metric without an owner is a metric with as many definitions as it has consumers.

Write the definition where people will read it

A definition buried in a wiki nobody visits does not exist. Put it next to the number: a tooltip on the dashboard tile that states the date basis, the exclusions, and the owner's name. It costs an afternoon and it ends most of the arguments, because the disagreeing parties can see immediately which choice differs.

Version the changes

Definitions legitimately change — a new revenue standard, a restructured product hierarchy, a decision to start excluding a channel. When they do, record the date the change took effect and keep the old definition readable. Otherwise a historical trend silently mixes two definitions, and the step change in the chart gets explained as a business event.

Certify a small set

Do not attempt this for every field in the warehouse. Pick the fifteen or twenty numbers that appear in board packs and executive reviews, govern those properly, and let everything else stay exploratory and clearly labelled as such. A small trusted set plus an honest 'uncertified' label beats a large catalogue nobody believes.

Discussion (2)

You
MD
Marcus D. Jul 23, 2026

Putting the definition in a tooltip next to the number ended about 80% of our reconciliation arguments. The remaining 20% turned out to be genuine disagreements about policy, which is exactly where they belonged.

FL
Fiona L. Jul 27, 2026

The versioning point saved us. We changed how we excluded internal orders and the year-on-year chart showed a 6% 'improvement' that finance nearly presented to the board as a result.

Ready for more?

Subscribe