Every Function Hit Its Number. The Enterprise Missed.

Every scorecard is green. The enterprise result is short.

The quarterly review runs ninety minutes. Sales presents against quota and makes it. Operations reports service levels inside target. Finance held spend to budget. Marketing delivered pipeline.

Each function has a slide. Each slide is green. Every leader in the room can defend their number.

Then someone puts up the enterprise result, and it is short.

Nobody lied. Nobody underperformed against what they were asked to deliver. The room goes quiet because there is no obvious place to put the problem.

This is often diagnosed as an alignment problem. The response is another alignment session or offsite. That rarely changes the result because the failure is not in how well the leaders understand one another. It is in what they are measured to deliver.

Clear priorities and decision authority still will not produce enterprise performance if leaders are measured against outcomes that pull them apart.

Leaders own what they can control

The mechanism is easy to miss because it starts with sound management practice.

We assign leaders measures they can control. Holding someone accountable for an outcome they cannot influence is unfair and ineffective. So sales gets bookings. Operations gets service level and cost per unit. Finance gets spend to plan.

Each measure can be controlled by one function. That is precisely why each can improve while enterprise performance gets worse.

The outcomes that matter most - margin realized on delivered revenue, customer retention, cash conversion, profitable growth - are produced by several functions acting together. Nobody controls them alone.

Under the controllability principle, no one may be measured on them. And what no one is measured on, no one owns.

The result is a leadership team where every individual measure is defensible, but the collection does not add up to the enterprise.

The divergence test

Take any leader's primary measure and ask one question:

Can this improve while enterprise performance gets worse?

Bookings can rise on deals that destroy margin. Cost per unit can fall by deferring maintenance. Spend can stay under plan by not hiring into a constrained function. Pipeline can grow with leads that never convert.

Run the question across the leadership team's primary measures. If the answer is yes across several of them, you do not have a shared enterprise scoreboard. You have a set of functional dashboards reviewed in the same room.

A collection of dashboards is not an enterprise scoreboard.

What makes the problem worse

Three conditions usually deepen the gap.

Volume. Measures accumulate until no metric holds attention long enough to produce a decision. Coverage replaces focus.

Availability. Teams select measures because the data is easy to access, not because the measure represents enterprise performance.

Definition drift. Two functions report the same metric using different definitions, and the review turns into a debate about whose number is correct.

What a shared view requires

Not more reporting. Fewer measures, better defined and differently owned.

Start with a focused set of enterprise measures small enough that every leader can name them without a document. Connect each measure to an enterprise priority. A measure that supports no priority may be tracked out of habit.

Assign one accountable owner to each measure. Several leaders may influence an enterprise result, but influence is not ownership. The question is who leads the response when the number goes the wrong way.

Then define the measure, the source, and what counts as off track before the review begins. Those decisions should not be negotiated while the team is trying to interpret performance.

The half that gets skipped

Getting the scoreboard right is the easier half. The harder half is what happens after a number turns red.

In many executive reviews, an off-track measure produces an explanation. The owner describes what happened, the team asks questions, everyone understands the situation better, and the meeting moves on.

Understanding is useful, but it is not action.

A performance exception should produce one of four outcomes: a decision, a commitment with a named owner and date, corrective action already underway, or an explicit choice to accept the risk.

Deliberately accepting a risk is a decision. Discussing a risk and taking no action is not.

If the last three performance reviews produced explanations but no decisions, the scoreboard may not be the constraint. The forum is.

Where to start

Ask each leader to write down, without conferring, the enterprise measures the business runs on.

Compare the lists. The overlap is the team's actual shared view.

Then compare what leaders named with what appears on the executive dashboard. The gap between the two will tell you whether the team is operating from a shared enterprise view or a collection of functional ones.