The Difference Between Having Data and Having Visibility

Observable condition

Managers know the information exists somewhere, yet a status question still starts a chain of messages, exports, reconciliations and spreadsheet updates. "How many orders are late?" "Which customers are at risk?" "What is our position this week?" Each question is answerable in principle. In practice, answering it means asking several people, pulling reports from several systems and agreeing which version is right.

By the time the answer arrives, the situation it describes may already have moved on, and a second round of questions begins.

Realisation

The business may have solved storage without solving visibility. Visibility requires consistent definitions, timely data movement and a view shaped around decisions rather than around the applications that happen to store the data.

The realisation is that "we have the data" and "we can see what is happening" are different claims. The first is about collection. The second is about whether the right people can see trustworthy, current facts at the moment they need to decide. Many organisations have invested heavily in the first and assumed the second would follow.

Identification

This is an operational visibility and decision-information design problem. The visible symptom is effort spent assembling answers. The common assumption is that a better reporting tool is needed. The structural cause is usually that definitions, ownership, timeliness and decision needs have not been designed together.

Diagnosis

Typical mechanisms include fragmented sources, inconsistent KPI definitions, delayed refresh cycles, manually maintained dashboards and weak data ownership.

A useful way to diagnose the gap is to test the data against recognised quality dimensions. The UK Government Data Quality Framework describes six: completeness, uniqueness, consistency, timeliness, validity and accuracy. It also frames quality as fitness for purpose, noting that trade-offs between dimensions are often necessary. Applied to visibility:

Consistency fails when departments calculate the same metric differently, so two reports disagree and a meeting is spent reconciling them.
Timeliness fails when data reflects last week while the decision is about today.
Uniqueness fails when the same customer or order appears more than once, inflating counts.
Completeness fails when key fields are optional in the source system and left blank.

Refresh cadence deserves particular attention. Business-intelligence tools can connect and refresh multiple sources, but the refresh is itself a design decision with limits. Microsoft's Power BI data refresh documentation, for example, explains that imported semantic models on shared capacity are limited to eight scheduled refreshes per day, rising to 48 on Premium, Premium Per User or Fabric capacity. Whatever the tool, a dashboard is only as current as its last refresh, and that cadence should be chosen to match the decision rather than accepted by default.

Ownership is the other recurring mechanism. When nobody is accountable for a field, nobody fixes it at source. Errors are corrected downstream, in the report or the spreadsheet, and the correction has to be repeated every time the data is pulled. Over time the corrected spreadsheet becomes the real source of truth, maintained by one person and invisible to the systems that are supposed to hold the data.

The useful operating design therefore starts with trusted definitions and decision cadence, not with charts.

Commercial impact

The value wrapper is decision speed, management capacity, risk and responsiveness. When visibility is assembled manually, management attention is spent locating and reconciling facts before acting on them. Problems are found later than they could have been, which narrows the options for responding. Skilled analysts become report assemblers, and confidence in the numbers erodes, so decisions are deferred while someone double-checks.

The cost compounds with growth. Each new product, site or channel adds another source to reconcile, and the effort needed to produce the same management view rises even though the questions have not changed.

Common misidentification

The symptom often triggers a dashboard project. A new dashboard built on inconsistent definitions merely displays disagreement faster. Equally, a data warehouse that gathers everything without agreed definitions or owners simply relocates the confusion.

Possibility

A stronger state identifies the few operational questions that matter, establishes accountable source fields and definitions, and refreshes them at a cadence appropriate to the decisions. In that state, a manager can see a signal, trust its definition, know how old it is, and move from the summary to the underlying transactions without another request. Visibility in this sense is deliberately narrow: a small number of well-defined views that people rely on, rather than a large number of reports that each need explaining.

Intervention

Start with a recurring management question, not a reporting tool. Then work through it deliberately:

Write the question down precisely, including the decision it supports and how often that decision is made.
Trace every input used to answer it today, including spreadsheets and messages.
For each input, record the source system, owner, definition and age at the moment of use.
Identify where definitions disagree and agree one definition, with a named owner.
Choose a refresh cadence that matches the decision, and make the data's age visible wherever it is displayed.
Automate the minimum data flow necessary to make the answer reliable, then retire the manual workaround.

Practical diagnostic: warning signs

Routine questions are answered by messaging people rather than by looking.
Meetings begin with a debate about whose numbers are right.
Important reports are rebuilt in spreadsheets each week or month.
Nobody can say how old the figures on a dashboard are.
Different departments report different totals for the same thing.
Problems are discovered through customer complaints before internal reports show them.
The person who maintains the key report is a single point of failure.

Practical diagnostic questions

Which questions repeatedly require manual data gathering?
Do departments define key metrics consistently?
How old is the data when a decision is made?
Which source is authoritative for each metric?
Can a manager move from signal to underlying transaction without another report request?

Bottom line

Having data means the facts exist. Having visibility means the organisation can see the right facts, with enough trust and timeliness to act. The gap between the two is closed by definitions, ownership and cadence designed around decisions, not by more storage or more charts.

Sources and further reading

The Government Data Quality Framework (last verified 10 October 2026)
Data refresh in Power BI - Power BI (last verified 10 October 2026)
On-premises data gateways in Power BI - Power BI