When Leaders Don’t Trust the Numbers, They Don’t Trust Each Other — And Here’s What Fixes It

I sat in a quarterly leadership meeting last year where five department heads presented their results. Every single one of them showed green on their dashboards.

Then the CEO asked a simple question: “If everything is green, why are our customers leaving?”

Silence.

This is what happens when every department builds its own measurement system in its own silo. Everyone is optimizing their own numbers. Nobody is looking at the same picture.

The scope of the problem

Research shows that 82% of companies lack unified success metrics across departments. Think about that. More than eight out of ten organizations don’t share a common definition of success across their leadership team.

The downstream effects are predictable. Sixty-five percent of project failures stem from poor cross-functional communication. Employees waste over five hours per week waiting for data from colleagues or recreating information that already exists somewhere else. Fortune 500 companies lose an estimated $31.5 billion annually by failing to share knowledge across teams.

But the number that should alarm leaders most is this: coordination costs consume an estimated 50-80% of management time in siloed organizations. That’s not a data problem. That’s a leadership capacity problem disguised as a data problem.

The trust erosion that nobody talks about

When I work with leadership teams, the surface-level complaint is usually about data quality or system incompatibility. But underneath, the real issue is trust.

When the sales team’s numbers don’t match the finance team’s numbers, each side suspects the other of spinning the data. When operations reports green and customer service reports red, someone is wrong — and the conversation quickly becomes about who, not why.

Data misalignment doesn’t just create confusion. It creates suspicion. And once suspicion takes root in a leadership team, it’s extraordinarily difficult to dislodge.

The root cause is simpler than you think

The temptation is to solve this with technology — a new BI platform, a data warehouse, a single source of truth. And yes, unified data infrastructure matters. But in our experience, the problem starts earlier than that.

It starts with definitions.

A few months ago, I was working with the leadership team of a regional services organization when a familiar argument erupted. The VP of Sales insisted that customer satisfaction was trending upward. The VP of Operations said it was flat. The VP of Customer Experience said it was declining. Each of them had data. Each of them had dashboards. Each of them was confident.

When we dug into it, we found the reason: the three departments were using eleven different definitions of “customer satisfaction.” Sales was measuring post-purchase survey scores. Operations was measuring service-level agreement compliance. Customer Experience was measuring Net Promoter Score plus a proprietary loyalty index.

They had been arguing about whose numbers were right for eighteen months. The answer was that all of their numbers were right — within their own definitions. The problem was that nobody had ever aligned on a shared definition. They were not having a data disagreement. They were having a language disagreement that looked like a data disagreement.

What does “on track” mean? What does “at risk” mean? When you say “customer satisfaction is up,” up compared to what? Over what time period? Measured how?

In most organizations, these foundational definitions have never been aligned across departments. Each team created its own metrics, its own dashboards, and its own narrative — in good faith — but without a shared vocabulary.

The framework: Shared Operating Metrics

The organizations I have seen resolve this problem consistently follow a three-step process. It is not glamorous. It does not require new technology. It requires discipline and, more importantly, it requires leaders to sit in a room and do the uncomfortable work of agreeing on what words mean.

Step one: Common definitions.

This is the foundation, and it is where most organizations skip ahead. Before you unify dashboards, unify language.

Gather your leadership team and identify the five to seven metrics that matter most to organizational performance. Then define each one precisely. What does “on track” mean? What does “at risk” mean? When someone says “customer satisfaction is 85%,” what is being measured, over what time period, from what data source, using what methodology?

The conversation itself is valuable, even before it produces a document. In the services organization I mentioned, the act of discovering eleven definitions for “customer satisfaction” was the breakthrough. The leadership team realized they had never had this conversation — not once in the organization’s history. Each department had built its metrics in isolation, in good faith, without ever checking whether their definitions matched anyone else’s.

Common definitions do not mean every department uses the same metrics internally. Departments still need specialized measures for their specific functions. But the metrics that go to the leadership team — the ones used to make strategic decisions — must mean the same thing to everyone in the room.

Step two: Shared scorecards.

Once you have common definitions, the next step is shared ownership. The key outcomes that matter most — customer retention, revenue growth, operational quality, employee engagement — should be jointly owned by multiple departments.

This is where the incentive structure shifts. When the customer retention number belongs only to Customer Experience, other departments can treat it as someone else’s problem. When that same number appears on the scorecards of Sales, Operations, and Customer Experience simultaneously — when all three leaders are evaluated partly on the same outcome — the dynamic changes fundamentally.

Shared scorecards do not eliminate departmental accountability. Each function still owns its specific contributions. But the outcomes those contributions are designed to produce become collective. The question shifts from “are my numbers good?” to “are our numbers good?” That is not a semantic distinction. It is a structural one. (See also: The Accountability Crisis Hiding in Plain Sight.)

Step three: Cross-functional data reviews.

This is the practice that makes the first two steps stick.

Monthly sessions where departments present the same data together. Not separately. Not sequentially in a slide deck where each VP presents their own dashboard. Together, looking at the shared scorecards, discussing the same numbers, in the same room, at the same time.

The difference is significant. When departments present separately, each one controls its own narrative. The numbers are curated. The story is managed. The uncomfortable data points get buried in appendix slides.

When departments present together, the narratives have to reconcile. If Sales says the pipeline is strong and Operations says delivery capacity is maxed, those two realities have to be discussed in real time. The conversation becomes about the organization’s actual situation rather than each department’s preferred version of it.

The trust dividend

There is a deeper effect that goes beyond efficiency.

Shared Operating Metrics reverse the suspicion dynamic. When everyone is looking at the same scoreboard, the arguments about whose numbers are right disappear. The energy that was consumed by reconciliation and suspicion gets redirected to analysis and decision-making.

The leadership team that had been arguing about eleven definitions of customer satisfaction for eighteen months resolved it in a single working session. They chose one definition, built one shared scorecard, and committed to a monthly cross-functional review. Six months later, the VP of Sales told me: “We used to spend the first twenty minutes of every leadership meeting arguing about data. Now we spend that time making decisions.”

That is the trust dividend. It is not just efficiency. It is the restoration of a leadership team’s ability to function as a team.

In our consulting practice, we have seen organizations reduce coordination costs by 25-40% within the first year of implementing monthly cross-functional reviews around shared scorecards. Not because the reviews themselves are magic, but because they create a forcing function for alignment. When you know you will be in the same room looking at the same numbers every month, you start aligning before the meeting, not during it.

This sounds straightforward — and it is. The challenge is not complexity. It is the courage to sit in a room and admit that you have been operating without shared definitions, and the discipline to build them. Have you been in that meeting where every dashboard is green but something is clearly broken? What would it take to get your leadership team looking at the same scoreboard?

Sources

• Stanford Organizational Research — Coordination Costs in Siloed Organizations (Robert Sutton)
• Fortune / Knowledge Management Research — $31.5 Billion Annual Knowledge Sharing Losses
• Cross-Functional Communication Research — Project Failure Rates (65% attributed to poor cross-functional communication)
• Productivity Research — Employee Time Lost to Data Reconciliation (5.3 hours/week)

Gordon Klein is the founder of Reflect Excellence, a leadership and organizational performance consulting firm. He serves on the Sterling Council board and contributes to the design of Sterling’s Leadership Development curriculum. He works with organizations across sectors — healthcare, government, education, and business — on the systemic challenges that make leadership harder than it needs to be. Connect with him to continue the conversation. (See also: Breaking Silos — What Actually Works.) (See also: What If the System Is the Problem?.)