What success should mean
- — Data Objects
A platform should not be judged mainly by terabytes stored, connectors deployed, or dashboards produced. More meaningful indicators include:
- time required to discover and understand a relevant asset;
- proportion of critical attributes with explicit lineage;
- percentage of recurring questions answered from governed products;
- mean time to detect and resolve data incidents;
- effort required to onboard a new source into an existing semantic model;
- number of conflicting definitions for the same business concept;
- ability to replay a computation and obtain an explainable result.
We can summarise platform maturity as a reduction in expected answer cost:
where Q is the distribution of legitimate future questions. The expectation is crucial. A platform is an investment in classes of future inquiries, not merely in today’s reporting backlog.
The phrase “too much data, too few answers” describes a structural failure to convert inscriptions into warranted, reproducible claims. The remedy is not indiscriminate centralisation. It is the construction of a computational and institutional layer in which identities, meanings, time, quality, provenance, and permitted use are explicit.
A cultivated Data Platform does not abolish interpretation. It disciplines interpretation. It does not promise that every question has an answer. It makes visible what evidence exists, how it has been transformed, what uncertainties remain, and which conclusions are justified. In this sense, the deepest product of a Data Platform is not a dataset or dashboard. It is an organisational capacity for accountable inquiry.
*Conceptual references
Bateson, G. Steps to an Ecology of Mind (1972). Bowker, G. C., and Star, S. L. Sorting Things Out (1999). Floridi, L. The Philosophy of Information (2011). Shannon, C. E. “A Mathematical Theory of Communication” (1948). Wiener, N. Cybernetics (1948).*
- 01. Too Much Data, Too Few Answers
- 05. The question as an architectural object
- 06. The politics of definitions
- 07. What success should mean
- 02. A Data Platform Is Not Another System to Use
- 03. The Data Platform as an Organisational Control Room
- 06. Multi-loop governance
- 07. Visibility, power, and ethical limits
- 08. The architecture of a credible control room
- 04. The Hidden Cost of Fragmented Data
- 06. Risk, audit, and the cost of explanation
- 07. The philosophical structure of fragmentation
- 08. Stable contracts as real options
- 05. Why Putting All Data in One Place Is Not Enough
- 06. Every Source Speaks a Dialect
- 06. Preserving the original expression
- 07. Late binding as translational ethics
- 08. Dialects evolve
- 09. The politics of the interlanguage
- 07. From Collecting Data to Producing Answers
- 08. The Business Value of a Data Platform: Efficiency, Quality, and Innovation
- 10. The counterfactual business case
- 09. Separating the Fact from the Local Format
- 10. Data Is Not the Table That Contains It
- 11. Dismantling the Source, Reconstructing Information
- 06. Idempotence and replay
- 07. Quarantine as a third state
- 08. Recomposition is not a return to the source
- 09. The philological analogy
- 12. What Is a Data Object?