The business has more dashboards, more reporting and more places to see what is happening than it did a few years ago.
Yet getting a straight answer can take longer.
A status shown in one system needs explaining against another. A dashboard says one thing, while the team closest to the work adds context that changes the picture. Leadership asks for another view because the existing ones still don’t quite answer the question.
The intention was greater visibility. What has grown alongside it is the effort required to work out what that visibility actually means.
That distinction matters because visibility increases but control does not surprisingly easily.
What this usually looks like in practice
Nothing necessarily appears badly designed.
A delivery team has its planning tool. Finance has another view. Risk, operations and senior management each have their own reporting needs. Larger programmes may have portfolio dashboards sitting above all of them; smaller businesses often arrive at much the same place by adding systems as particular needs arise.
Each addition can make perfectly good sense on its own. The problem tends to show up in the gaps between them.
Numbers need reconciling before meetings. Somebody knows why one dashboard is a day behind another. A red status needs explaining because the underlying issue is already being dealt with elsewhere; a green one carries a qualification that never made it into the metric.
So the organisation has plenty of information. What it does not necessarily have is one dependable view of the position.
That is when reporting increases but outcomes do not improve with it.
More visibility is not the same as more understanding
A system can make one part of delivery much easier to see without making the whole easier to understand.
This becomes more obvious as work crosses functions, suppliers, business units or regions. Each part may be visible in considerable detail, while the condition created between those parts remains difficult to see.
The question then changes from, “Do we have the information?” to, “Can we tell what is actually happening from it?”
More data can reveal more individual facts while making their relationship harder to interpret. More reporting can expose more activity without making it any clearer which activity is actually changing the outcome.
And project metrics do not have to be obviously wrong to stop reflecting reality properly. Sometimes they are simply incomplete enough that somebody has to interpret them every time they are used.
That is easy to miss because nothing looks absent. In fact, there is often more to look at than ever.
The work starts moving between the systems
Once the formal systems stop providing a sufficiently coherent picture on their own, people bridge the difference.
They export information, reconcile figures, update duplicate fields and carry context from one conversation into another. The unplanned work becomes the work required to make the formal information usable.
A spreadsheet appears because two systems cannot quite produce the same answer. A weekly meeting becomes necessary because the dashboard needs explaining. One person gradually becomes indispensable because they know which figure can be trusted and which one needs qualification.
By then, the organisation is paying for more than its systems. It is also paying people to make those systems intelligible to one another.
That effort rarely presents itself as a problem. It looks like normal coordination, and individually most of it probably is. The issue is how much capacity it starts to absorb once that coordination becomes a permanent part of running the environment.
Control starts depending on effort
This is where governance pressure starts to build.
More checks are introduced because confidence in the existing picture is weak. Reporting becomes more detailed, reviews become more frequent and people spend more time reassuring others that the position is understood.
Looking in from outside, that can look like stronger control. Sometimes it is. Sometimes it is simply more effort being used to compensate for a view that is not reliable enough on its own.
The distinction matters when reporting is not matching actual delivery closely enough for leaders to use it without repeated explanation. Confidence then rests partly on people joining the dots every week.
That can sustain the appearance of control for quite a while, which is also why delivery confidence can weaken before anything looks like formal failure.
The information environment still looks active and well populated. What has changed is the amount of effort needed to keep the picture credible.
And once those workarounds become familiar, they tend to acquire a life of their own. Additional reporting becomes normal, reconciliation becomes part of the weekly rhythm and the organisation gradually builds operating assumptions around both.
The commercial consequence arrives quietly
There is rarely one obvious line item labelled “cost of understanding our own reporting”.
Instead, it appears as management attention, repeated reconciliation, duplicate handling, additional governance and time spent getting comfortable with the position before acting on it.
None of those things has to be wasteful in isolation. The commercial issue is what happens when they accumulate.
An hour spent reconciling two views is an hour not spent changing the underlying outcome. A leadership meeting that spends twenty minutes establishing which number is right has twenty minutes less for the decision that number was meant to support.
Across a large programme, that can absorb considerable capacity. In a scaling business, the absolute numbers may be smaller but the effect can arrive faster because fewer people are available to carry the extra work.
This is where the adjacent commercial signal starts to show: confidence is being maintained through effort rather than through the reliability of the underlying view.
The systems themselves may still be doing exactly what they were bought to do. The organisation is simply carrying more of the integration between them than it realises.
The number of systems is not the useful test
A business with ten systems can have excellent control. Another with three can struggle.
The useful test is how much human effort sits between the information and a confident answer.
Can someone establish what is actually moving, what is not, which figure describes the current position and where a decision is required without first reconciling several versions of reality?
If the answer increasingly depends on private spreadsheets, repeated explanations, corridor knowledge or the person who “knows how it all fits together”, the issue is not simply reporting volume.
The organisation has increased its representations of reality faster than its ability to turn them into one reliable view.
More visibility has not produced more control. It has created more work in the gap between the two.
Where is effort being absorbed without producing equivalent progress?
If that is difficult to see from the existing reporting, the Full Delivery Scorecard provides a useful next diagnostic view.
Related Observations
Delivery Confidence Drops Before Failure
When confidence increasingly depends on explanation and reassurance, the visible status can remain stable after the underlying position has started to weaken.
Read the observation
Programme Scale Changes Delivery Stability
As delivery spans more teams and boundaries, the relationships between individual views matter as much as the quality of each view itself.
Explore programme-scale delivery stability
Work Can Keep Moving Without Progress Building
Visible activity can remain high even when the organisation is spending more effort maintaining movement than converting it into outcomes.
See why work can keep moving without progress building
Effort Does Not Always Convert Into Progress
When additional capacity is repeatedly absorbed at the same points, increasing effort can hide the condition rather than resolve it.
See where effort stops converting into progress