Why Leadership Teams Have Conflicting Metrics – How to Fix Them

The leadership meeting is meant to decide whether to invest, intervene or change course. Instead, it stalls over conflicting metrics – the wrong numbers.

Finance has one revenue figure. Sales has another. Operations is reporting a different customer volume, while the service team questions whether the customer base being discussed is even the same one. Each function can show where its number came from and each can explain why it is reasonable.

The debate around conflicting metrics consumes the meeting. People defend their reports, promise another reconciliation exercise and postpone the decision that the meeting was convened to make. By the following month, the same disagreement returns with a refreshed set of slides.

This is often described as a data-quality problem. It is, but that description is incomplete. When a leadership team cannot agree which numbers are right, the organisation also has a decision-control problem. It does not know which evidence is authoritative for which purpose, why competing measures differ or who has the authority to resolve the disagreement.

Conflicting Metrics do not always mean that somebody is wrong

A number can be accurate within one system and still be unsuitable for the decision in front of the leadership team. Sales may count a customer when an opportunity is contracted. Finance may recognise revenue only when particular accounting conditions are met. Operations may count an active account when a service is provisioned, while customer success may use product usage or renewal status.

The same problem appears in familiar measures such as pipeline, revenue, margin, churn, active customers, on-time delivery and project completion. The label is shared, but the definition, period, unit of analysis, exclusions or source can differ.

That distinction matters because the wrong objective is often pursued. Leaders ask, ‘Which number is the real one?’ when the better question is, ‘Which number is fit for this decision, and can we explain how it relates to the others?’

The Government Data Quality Framework defines quality in terms of fitness for purpose. It also stresses that poor or unknown quality weakens evidence, undermines trust and impedes effective decision-making. That is more useful than the pursuit of a supposedly perfect universal number. Leadership needs evidence that is good enough, clearly defined and controlled for the decision being made.

Why leadership reporting produces conflicting truths

Conflicting metrics are rarely caused by one dramatic failure. They usually emerge from several reasonable local choices that have never been reconciled at enterprise level.

The same word carries different definitions.

A ‘customer’ might mean a legal entity, billing account, contract, operating site or active user group. A ‘renewal’ might mean a signed agreement, a verbal commitment, a forecast category or revenue recognised in a later period. Unless the business definition is explicit, shared language creates an illusion of agreement.

Systems record different stages of the same journey.

CRM, finance, service, product and operational systems are built for different jobs. Their records are often legitimate, but they capture different events and update at different times. The leadership pack then compares outputs that were never designed to reconcile automatically.

Cut-off dates and calculation rules are hidden.

A month-end report, live dashboard and manually adjusted forecast can all display the same metric name while using different time boundaries. Gross and net values may be mixed. Currency, exclusions, cancellations, credits or late entries may be handled differently without being visible in the headline figure.

Manual reconciliation becomes part of the operating model.

Spreadsheets, extracts and management adjustments often begin as sensible fixes. Over time, they become undocumented bridges between systems. The organisation can still produce a number, but confidence increasingly depends on the people who know how the bridge works.

Ownership stops at the report.

One team owns the source system, another produces the dashboard and several functions consume the result, yet nobody is accountable for the business meaning and fitness of the measure from source to decision. When a conflict appears, everyone can explain their part without anyone owning the whole.

The cost appears before the data problem is fixed

The visible symptom is disagreement in a meeting. The wider cost is the behaviour that disagreement creates across the business.

Decisions slow down because leaders cannot distinguish genuine uncertainty from reporting inconsistency. Forecasts become negotiated positions rather than controlled views. Functions create parallel reports to protect themselves. Analysts spend time rebuilding confidence instead of generating insight. Accountability weakens because performance can be explained through whichever number best supports the argument.

McKinsey’s 2023 master-data survey found that 80% of responding organisations had divisions operating in silos with their own data practices, systems and consumption behaviours. It also found that 82% of respondents spent at least one day each week resolving master-data quality issues, while 66% relied on manual review. The significance is not the precise percentage in any one organisation. It is that reconciliation can quietly become routine work rather than an exception to be removed. See the McKinsey analysis.

The conflicting metrics exposure grows when automation or AI begins to act on the same fragmented foundations. A human can sometimes notice that two dashboards disagree. An automated workflow may simply use the source it has been given and propagate the inconsistency into pricing, prioritisation, customer treatment or operational decisions.

IBM’s 2026 analysis describes how poor-quality data often appears downstream as lost revenue, inefficiency, compliance risk and missed opportunity rather than at the original point of failure. It also notes that 43% of COOs in an IBM Institute for Business Value study identified data quality as their most significant data priority. The leadership implication is clear: unresolved disagreement is not an untidy reporting issue. It is an early control warning. Read the IBM analysis.

What not to do when you have conflicting metrics

Do not settle the conflicting metrics issue by choosing the most senior person’s preferred report. Authority can make a number official without making it suitable.

Do not ask for another dashboard before agreeing the decision, definition and source. Better presentation can make uncontrolled evidence look more credible without improving it.

Do not hand the problem to technology alone. Technical teams can trace systems, transformations and integrations, but business leaders must decide what the measure means, what standard it needs to meet and which trade-offs are acceptable.

Do not wait for perfect enterprise data before making any decision. Some uncertainty will remain. The leadership responsibility is to make that uncertainty visible, choose a proportionate interim rule and stop the same unresolved argument from recurring.

A practical route from conflicting metrics to control

The objective is not to make every report identical. Different functions may legitimately need different views. The objective is to control the relationship between those views so the leadership team knows which one is authoritative for a particular decision.

1. Start with the decision, not the dashboard

State the decision that the leadership team needs to make and the consequence of being wrong. A pricing decision may require recognised revenue and margin at a specific level. A capacity decision may need live demand and operational workload. A renewal intervention may need contract value, usage, service effort and customer risk together.

This follows the discipline in Oak’s Evidence-Led Leadership: begin with the leadership question and work backwards to the evidence needed. Available data should not be allowed to define the question simply because it is easy to report.

2. Put the competing measures side by side

For each disputed number, record its business definition, source system, calculation, cut-off, level of detail, exclusions and any manual adjustment. Do this visibly and without beginning from the assumption that one function has failed.

Many disagreements become understandable at this point. The figures may describe different stages, populations or time periods. That does not remove the need for control, but it turns an argument between functions into a specific difference that can be resolved.

3. Create a decision-grade metric contract

For each critical leadership measure, agree a short operating definition that answers six questions: what exactly is being measured, why it matters, which source is authoritative, how it is calculated, how current it must be and who is accountable for its business meaning and quality.

The contract should also explain legitimate alternative views. For example, booked revenue, recognised revenue and cash received can all remain useful, provided the leadership pack does not present them interchangeably.

4. Separate ownership from technical custody

The Government Data Ownership Model makes a useful distinction between senior data owners, who are accountable for meaning, quality and management, and operational stewards or custodians who manage data day to day. Although written for government, the principle transfers well to B2B organisations.

The owner should be a business leader with enough authority to resolve competing requirements. Technology supports the control, but the business cannot outsource the meaning of revenue, customer, margin, service performance or commercial risk.

5. Make confidence and uncertainty visible

A leadership pack should not imply equal certainty across every measure. Mark a critical figure as controlled, provisional or disputed, explain the material limitation and state the action under way. This is more useful than false precision and safer than a footnote that nobody reads.

Where a decision cannot wait, record the temporary rule: which measure will be used, why it is the least-risk basis available, what could change the conclusion and who will resolve the remaining gap by when.

6. Fix the recurring cause at source

Once the immediate decision is protected, trace the disagreement back through the data lifecycle. Correct definitions, entry controls, integrations, mappings and manual adjustments where they originate. Retire duplicate reports when they no longer serve a distinct purpose.

The Government Data Quality Framework recommends treating issues at source, using root-cause analysis and maintaining ongoing monitoring rather than relying on repeated cleaning. That turns reconciliation from a monthly ritual into a controlled exception.

A focused 90-day leadership reset

A full enterprise-data programme may be justified, but it is rarely the best first response to one leadership team’s loss of confidence. Begin with the measures carrying the greatest decision, customer or commercial consequence.

Days 1-30: identify the critical decisions and measures.

Select the small number of figures that repeatedly create disagreement or materially affect capital, customers, delivery or risk. Record the competing definitions, sources, adjustments, known limitations and time being lost to reconciliation.

Days 31-60: agree ownership and control.

Name a senior business owner for each measure, agree the decision-grade definition and establish how alternative views connect. Resolve the highest-risk differences and define the temporary rules for any uncertainty that remains.

Days 61-90: embed the controlled view.

Update leadership reporting, introduce proportionate quality checks, make exceptions visible and retire unnecessary duplicates. Review whether meetings are spending less time debating the evidence and more time making the decisions the evidence is meant to support.

Oak’s Data Integrity in B2B: From Noise to Trust develops this wider leadership challenge through the A+B+C Architecture, Data Integrity Radar and a practical 90-day control reset.

Five questions for the next leadership meeting

What decision is this number meant to support?

A figure can be reliable for one purpose and misleading for another. Start with the consequence and the evidence standard it requires.

Are we disagreeing about the value or about what the measure means?

This separates a genuine data error from a definition, timing or scope difference.

Can we trace each figure from source to report?

Make transformations, exclusions and manual adjustments visible enough to be challenged and reproduced.

Who owns the business meaning and fitness of this measure?

Producing the report or operating the system is not the same as being accountable for the measure used to govern the business.

What rule will protect today’s decision while the underlying issue is fixed?

Visible uncertainty with a named owner and deadline is safer than either invented certainty or indefinite delay.

The leadership implication

Enterprise truth does not require one number for every purpose. It requires the organisation to know which view is authoritative for the decision, why legitimate views differ and who owns resolution.

The same principle sits behind Oak’s article No One Owns Customer Truth – So Nothing Improves. Contradictory functional views can coexist when nobody owns reconciliation, leaving the business unable to learn and act.

A leadership team that keeps arguing about the numbers should resist the urge to demand a more confident presentation. The disagreement is useful evidence of weak definitions, ownership or control. Make it explicit, protect the immediate decision and remove the recurring cause at source.