Visibility Is Not Reporting: The Real-Time Operating Picture

Most organisations invested properly in reporting. The warehouse got built, the BI tool got rolled out, and the pack that reaches the executive table each month reconciles to the ledger. The numbers in it are correct. That work was worth doing.

It also answered one specific question: what took place, across a defined window, in a form that can be signed and defended. Financial reporting exists to meet that requirement and it meets it well. But it is not the question an operations leader carries into a Tuesday morning, which sounds more like: what is going on right now, and what is about to go wrong?

Both answers get called visibility. Only one of them is.

Two Questions That Look Alike

The distinction is neither new nor a marketing frame. It was formalised in the early 1990s, when Robert Kaplan and David Norton argued that financial measures on their own gave managers a distorted view of performance. Their Balanced Scorecard work treated operational measures as leading indicators and financial metrics as lagging outcomes.

Kaplan was explicit about what separates them, describing how a quantified model would estimate "the time delay between a 1% improvement in a leading indicator and the expected response in a lagging indicator." That delay is the whole issue. A lagging measure is not a lower-quality metric; it is an accurate measure of something that has already finished.

It is easiest to see one domain at a time.

The pattern holds across all of them, and it explains something that looks like an editorial choice but isn't. The lagging measure is the one that gets reported because it is the one that reconciles: checked, allocated, agreed. The leading signal sits in an operational system, unreconciled and therefore untrusted, so it never reaches the pack. Reporting selects for what can be signed off, which is precisely the set of things that are already over.

The Lag Sits in the Pipeline, Not the Report

Faced with a picture that keeps arriving late, the instinct is to fix the reporting: a better tool, a cleaner layout, a faster refresh. That rarely helps, because the delay was never in the report. It accumulated in the chain the numbers travelled through to get there.

Every link in that chain is individually defensible. Batch windows exist because continuous extraction is expensive. Reconciliation exists because two systems genuinely disagree about the same record. Review exists because a number going to a board ought to be checked. None of it is negligence. It simply adds up.

The absolute figure matters less than one comparison: is your picture younger than the decisions you make on it? A five-day-old view is perfectly adequate for a capital allocation decision and useless for a delivery promise you have to keep on Thursday. The same reporting layer can be sufficient and insufficient at once, depending on which decision is asking.

What Deciding Late Costs

McKinsey surveyed more than 1,200 managers on how decisions actually get made. Only 20% said their organisations excel at decision making, and on average 61% said most of the time they spend making decisions is used ineffectively. Scaled to a typical Fortune 500 company, the firm estimated this represents more than 530,000 days of lost working time and roughly $250 million in wasted labour costs per year.

Stale data is not the sole cause of that, and it would be dishonest to present it as one. But a recognisable share of the waste has the same shape: meetings convened to establish what is going on, decisions deferred until the next pack lands, positions re-argued because two teams brought different numbers. When the picture is old, organisations substitute discussion for information.

The reverse case has evidence behind it too. Studying 179 large public companies, Brynjolfsson, Hitt and Kim found that firms adopting data-driven decision making showed output and productivity 5–6% higher than their other investments and IT usage would predict.

Why Another Dashboard Does Not Close the Gap

A reporting layer inherits whatever sits underneath it. The MuleSoft 2025 Connectivity Benchmark puts the average organisation at 897 applications, with only 2% having successfully integrated more than half of them, while 90% of IT leaders say data silos are creating business challenges.

Visualisation over an estate like that does not yield an operating picture. It yields a well-rendered summary of whichever slice could be extracted and reconciled in time, which is exactly why the reconciliation step is where the days disappear. The dashboard is not the weak link. It is a faithful rendering of a fragmented foundation, delivered as fast as that foundation allows.

This is the same fragmentation we put a number on in The Integration Tax, surfacing here as latency rather than cost, and it lives in the unowned space between systems described in The Operational Last Mile.

What an Operating Picture Requires

Reporting is not the thing to remove. Governance needs a periodic, reconciled, defensible account of what happened, and that need is permanent. What has to change is the expectation that the same artefact can also tell you what to do next.

An operating picture is a different construct, with four properties:

• Event-driven rather than scheduled — the record changes when work changes state, so there is no window to wait for.
• Work state rather than outcomes — the unit is the order, case, or shift currently in flight, not an aggregate of the ones that closed.
• One record across systems — reconciliation happens once, in the layer, instead of by hand ahead of every report.
• Drill-through to something actionable — from a signal to the specific customer, job, or person someone can pick up today.

None of those are reporting features. They are properties of the operational layer beneath the reporting, which is why buying another analytics tool never delivers them, and why the two capabilities are built in different places. That layer is also what makes automation viable later; acting on a picture that is days old is how automation compounds errors instead of work.

The Path Forward

There is no need to choose between reporting and visibility. What matters is stopping one from being asked to do the other's job.

The practical starting point is deliberately narrow. Pick a single decision you consistently make later than you would like. Identify the leading signal that would have flagged it earlier, find which system that signal already lives in, and count the steps between there and the person who needs it. That count is your real reporting architecture, and it is usually shorter to fix than it appears, because the signal nearly always exists already. It just never survives the trip.

Then leave the month-end pack exactly as it is. It was never the problem. It was only ever the wrong instrument to steer by.

Want a live operating picture instead of a monthly reconstruction? Start the conversation — we'll map the decisions you make late and show you where the signal already exists in your systems.

---

Sources

1. Robert S. Kaplan. Conceptual Foundations of the Balanced Scorecard. Harvard Business School Working Paper 10-074, 2010. hbs.edu — describes non-financial operational measures as "leading indicators and financial metrics as lagging outcomes", and the modelling of "the time delay between a 1% improvement in a leading indicator and the expected response in a lagging indicator".

2. McKinsey & Company. Decision Making in the Age of Urgency. April 2019. mckinsey.com — of 1,228 respondents familiar with decision making at their organisations, only 20% say their organisations excel at it and, on average, 61% say most of their decision-making time is used ineffectively; at an average Fortune 500 company this is estimated at more than 530,000 days of lost working time and roughly $250 million of wasted labour costs per year.

3. Erik Brynjolfsson, Lorin M. Hitt and Heekyung Hellen Kim. Strength in Numbers: How Does Data-Driven Decisionmaking Affect Firm Performance? 2011. SSRN; also published in ICIS 2011 Proceedings — using survey data on 179 large publicly traded firms, firms adopting data-driven decision making show output and productivity 5–6% higher than would be expected given their other investments and information technology usage.

4. Salesforce / MuleSoft. 2025 Connectivity Benchmark Report. 2025. MuleSoft blog summary — average of 897 applications per organisation; only 2% have integrated more than half of their applications. Salesforce newsroom — 90% of IT leaders say data silos are creating business challenges.