Observable condition
Sales reports one conversion rate, finance uses another revenue figure, operations counts a completed order differently and management meetings begin with people reconciling numbers. Everyone may be using technically valid data while still measuring different things under the same label.
Realisation
This can look like a reporting-tool problem. But when multiple systems or teams calculate a metric differently, changing the dashboard only relocates the disagreement. The deeper question is whether the organisation has defined what the metric means, which events count, which exclusions apply, which time period governs it and who has authority to maintain that definition.
Identification
This is a metric-definition and data-governance ownership problem.
Diagnosis
Common causes include calculations created independently by departments, undocumented filters, different source systems, changing business rules and no named owner for metric semantics. ISO 8000 treats information and data quality as something that must be understood, measured and managed through documented methods. A metric cannot be reliably automated or compared when its underlying meaning changes between users.
Commercial impact
The value wrapper is decision quality, management capacity, automation readiness and trust. Meetings are consumed by reconciliation. Teams can optimise against different versions of the same objective. Automated alerts and AI analysis can amplify confusion if the metric definition is ambiguous before technology is applied.
Common misidentification
The instinct is often to create a “single dashboard”. A common interface helps only after the business agrees what each measure means. A shared visual layer sitting on top of competing definitions can make inconsistency look authoritative rather than resolving it.
Possibility
A stronger operating model gives important metrics explicit semantic ownership. Each metric has a documented definition, source events, calculation logic, exclusions, refresh expectation and accountable owner. Systems can then implement the definition consistently instead of inventing it independently.
Intervention
Select five metrics that regularly create debate. For each one, ask two teams to write the calculation and business meaning without consulting each other. Compare the answers. Where they diverge, resolve the business definition first, then encode it in reporting or semantic-layer tooling.
Practical diagnostic questions
- Can two teams independently explain the metric and produce the same result?
- Who is authorised to change the definition?
- Which source event determines when something is counted?
- Are exclusions, time windows and denominators documented?
- Do dashboards reuse one definition or recreate calculations separately?
Bottom line
When nobody owns the definition of a business metric, the company can have more data and less agreement at the same time.
Sources and further reading
- ISO 8000-8: Information and data quality concepts and measuring
- ISO 8000-63: Data quality management process measurement