What disappears in the space between what a system does and the record it leaves behind.
The record is a projection of the system — not a copy of it.
The EVOLVRS Research series · Reads with The Measurement Gap (Position Paper 001)
Continues in Essay 02 · What if the data you need does not exist?
The projection
Every system leaves a trail — transactions, timestamps, tickets, logs, messages, and now the calls a model makes. It is tempting to treat that trail as the system itself, rendered in data. It is not.
A record is a projection. The system has been passed through an instrument, and only what that instrument was built to capture survives the pass. Everything it was not built to capture is absent — not hidden, not corrupted, simply never written down. The volume of the record has grown enormously; the volume of the system it represents has not grown with it. IDC forecasts the world's data creation expanding at roughly 25% a year through 2028.1 But volume measures the size of the projection, not its completeness. A larger shadow is still a shadow.
The recorded region sits inside the system. The margin around it is not missing data. It is the part no instrument was ever built to observe.
Instrumentation
This is not a flaw in any particular system. It is a property of instrumentation itself.
A finance system was built to capture money moving, so it captures money moving with great fidelity — and nothing about why a decision was made, how a handoff really happened, or what a team improvised to keep a broken process working. A ticketing system records tickets, not the conversation in the hallway that solved the problem before a ticket was ever opened. What gets instrumented is what was easy to instrument and consequential to bill, audit, or execute. The rest — the practice of the work — was left to memory.
And the rest is not a random remainder. It is disproportionately the part that explains why two units running the same system produce different results, because sameness in the record is exactly what the record was built to enforce. The systems of record are designed to make identical work look identical. The difference between two teams lives in everything those systems were built to hold constant.
Data-rich, information-poor
Two things have grown at once: the amount an organization records, and its confidence that recording is understanding. They are not the same growth.
Data and analytics leaders estimate that about a quarter of their own organizational data — 26% — is untrustworthy,2 and even the trustworthy remainder is still only the projection. An organization can therefore become, at the same moment, richer in data and poorer in information about itself: more is written down, and less of what actually matters is among it. This is the condition the rest of this series takes as its subject.
Closing the gap is not a matter of collecting the same kind of record more aggressively. It requires deciding what about the system is worth observing, and then building an instrument that observes it. That is a measurement problem, not a data problem.
When a question about a system cannot be answered, it is for one of three reasons: the observation exists but is scattered across systems; the observation exists but cannot bear the question; or the observation was never created at all. This essay is about the largest case — the part of the system that no instrument ever recorded. The next takes up the boundary between what can still be retrieved and what was never made.