A familiar ritual follows organisational trouble. A decision goes wrong, a delivery slips, a risk materialises that somebody somewhere had documented, and the retrospective lands on a convenient conclusion: the information wasn’t good enough. The remedy writes itself. Another dashboard. A new report. A data lake, properly governed this time. An AI pilot to surface insights. More policy on how information ought to flow.
The ritual is comfortable because it frames the problem as scarcity, and scarcity has an obvious cure. A walk through almost any large organisation suggests no shortage at all. Dashboards refresh nightly and go unwatched. The same metric appears in three decks with three different values. Reports run on schedules nobody remembers setting, for audiences nobody has confirmed still exist. Meetings re-litigate facts that were settled in other meetings. The organisation is not starving. It is standing in a warehouse of maps, unsure which one describes the territory outside.
What is often scarce is not information itself. It is confidence that the information means what it is taken to mean.
Four hundred suppliers, or nineteen hundred
Somebody asks how many suppliers the company has. Procurement says 400, the ones on its approved list. Finance says 1,900, every entity it has paid. Legal says 250, the ones with a negotiated contract rather than standard purchase order terms. The reflex is to hunt for the wrong one. There is no wrong one. A supplier is an obvious thing, obvious enough that nobody has written down what makes one, and three teams have settled it three different ways without noticing. That is not a data quality failure. It is an unreconciled meaning, surfacing as arithmetic.
Each of the three made sense where it was minted. The trouble starts when a word travels, carrying the confidence of home into a place where a different definition quietly holds. The same travelling has long kept business and ICT talking past one another.
An organisation in this condition can add information indefinitely without settling a single definition. Each new report is a new message, written in the local dialect of whoever built it, and each one raises the reconciliation bill for whoever reads it. The bill is never itemised.
Messages to the future
Stored data is “a message, a communication, to people in the future”. Ronald Ross has spent a career on business rules, and that is his compact description of it. A message implies a sender with an intent, a receiver who was not in the room when the intent formed, and a gap the message crosses alone.
Distance in time behaves like distance in space. The analyst who named the column has moved teams. The assumptions behind the metric were obvious to everyone in the room in 2019, and the room has dispersed. The report still arrives every Monday, fluent and confident, a message from senders who can no longer be asked what they meant. Each reader supplies a plausible meaning of their own.
Organisations rarely notice, because the compensating works well enough to stay invisible. Somebody always knows which version of a figure to believe. A pre-meeting reconciles the figures before the real meeting sees them. These compensations are genuine organisational competence, and they share one weakness: they live in particular people, and they go when those people do. What walks out the door is not information, which stays neatly in the databases. It is the knowledge of which number to trust, and why.
Custody of meaning
A message that has to survive its sender needs somewhere to be kept. Metier’s information life cycle has distinct stages: a landing zone for what is unverified and might be information, a staging area for what has been checked, a semantic stage where an intermediate form is shaped, and only then a product verified as fit for delivery. The stages read less like storage tiers than like a chain of custody. Data lineage traces the same chain backwards: where a piece of information came from, and what has been done to it along the way. At each stage, someone vouches: still what it claims to be, still meaning what it was minted to mean.
As plumbing, such a pipeline is easy to dismiss as ceremony, the boring part of ICT, keeping the lights on. As custody, it is the difference between a warehouse of maps and a map that can be trusted at the moment of stepping outside. A reliable message is one that complies with the rules of the context that produced it. Verification stops being bureaucratic caution. It is what keeps the message decodable after the sender has gone.
A figure can be trusted only as far as its meaning is maintained, and maintaining meaning is work, with owners, stages and failure modes of its own. Organisations often fund the production of information more visibly than the custody of its meaning.
Data and information are kept apart in Metier, and so is most of what everyday language runs together. The distinctions are filed by concern.
A count rarely taken
“What information was missing” almost always has an answer, which is part of its appeal. Something can always be named, and a report commissioned to supply it. A different count is seldom taken: of everything already held, how much gets acted on without a corroborating phone call.
Where most of it would be acted on, even a thin report goes a long way. Where little of it would be, no amount of additional reporting is likely to help. The appetite for one more dashboard rests on a scarcity that, in most organisations, ended years ago.