There is a default assumption embedded in how most organisations operate:
run the business well, and information will emerge.
Build the products. Serve the customers. Close the deals. Along the way, data accumulates — in spreadsheets, in systems, in people’s heads. When a decision needs to be made, the information is assumed to be there somewhere. It only needs to be found (I still remember those challenging Enterprise Search implementations)
For a long time, this assumption held.
In stable, predictable environments, experience functioned as a reliable proxy for information. Patterns repeated. What worked last year was likely to work next year. Senior leaders had seen similar situations before. Organisational knowledge resided primarily in people: in judgement built over time, in relationships, in institutional memory.
In that context, information could remain a by-product of work rather than the work itself.
That context no longer exists.
The inversion
We now operate in an information economy, but organisational design has not kept pace.
The raw material of value creation has changed; Information is both the raw material and the output. The way organisations are structured has not changed with that.
What “running the business” means today is fundamentally different:
- A retailer does not merely move products; it generates continuous information about customer behaviour, supply-chain performance, pricing sensitivity, and demand patterns.
- A manufacturer does not merely produce goods; it creates telemetry from sensors, quality metrics, maintenance data, and operational logs.
- A professional services firm does not merely deliver projects; it accumulates expertise, methodologies, client insight, and competitive knowledge.
In many cases, the information generated is more valuable than the transaction that produced it.
Yet most organisations still treat this information as exhaust: captured incidentally, stored unevenly, and rarely converted into reusable organisational knowledge.
Organisations that understand this inversion are designed differently.
Spotify, for example, does not merely distribute music. It operates as an information company that delivers audio. Every interaction feeds learning systems. Every playlist becomes training data. Every preference shapes downstream decisions. Music is the product; information is the asset.
Most organisations are not designed this way. They continue to treat information as something that emerges from “real work”, rather than as a core production activity in its own right.
Structural risk, not operational failure
Treating information as a by-product does not create isolated problems.
It creates structural risk.
These risks cannot be resolved with better tools. They are consequences of organisational design.
Loss of shared meaning
When information is captured incidentally, it is named inconsistently and contextualised poorly. Data remains available, but the meaning fragments. Reports are no longer trusted because metrics are interpreted differently across teams. Decision-making becomes political rather than informational — not because data is wrong, but because meaning was never agreed upon.
Fragile decision-making in volatile environments
If information is not produced deliberately, metrics lag reality, assumptions remain implicit, and early signals disappear into noise. Decisions default to experience, hierarchy, or intuition rather than evidence. This is a familiar symptom that can function in stable environments, where experience remains valid. In volatile environments like we are today, it collapses — because the patterns that made leaders successful no longer apply.
Unscalable knowledge
When information is embedded in tools and locked in silos, organisations become dependent on individuals: the person who built the model, the analyst who knows where the data lives, the IT teams who understand the technical aspect of the tool and finally the manager who remembers why a process exists. Growth amplifies fragility. Employee turnover or even reorganisation disrupts knowledge continuity. It all affects organisational memory.
Security and compliance exposure
Regulators increasingly expect organisations to know what information they hold, where it resides, and who is accountable. Many cannot answer these questions.
When ownership of information is unclear, lifecycle management is absent and sensitivity is implicit. Breaches occur not through intent, but through ambiguity.
Tool-driven complexity
When information is not designed, tools fill the vacuum. Each new problem generates a new platform, workflow, or workaround. Architecture expands while coherence declines.
AI amplification of dysfunction
AI does not correct poor information models; it amplifies them. Fragmented, poorly governed, context-free information produces confident output with little grounding and errors scale. Organisations deploying AI on unstable informational foundations are not accelerating intelligence — they are accelerating error. Hallucinations appear as insight.
Strategic blindness
When information is treated as a by-product, strategy loses contact with operational reality. Feedback loops become slow and distorted, forcing organisations into reactive behaviour. By the time issues appear in executive dashboards, they have already become systemic.
The maturity gap
Across data maturity models — from government frameworks to industry benchmarks — the pattern is consistent.
Most organisations operate at early stages of informational maturity. Information is used reactively, primarily for retrospective reporting. Quality is addressed locally. Governance remains fragmented. Data supports the organisation; it does not shape it.
Only at higher levels of maturity does information become a strategic capability: governed intentionally, produced deliberately, and embedded in decision-making. At that point, information flows are designed, not accidental.
The uncomfortable truth is that many organisations that describe themselves as “data-driven” remain stuck at the lower stages. They have dashboards, but not decisions. Platforms, but not discipline.
The limitation is not technological.
The limitation is organisational.
What deliberate information production looks like
The distinction between information as by-product and information as designed asset is observable.
- Ownership is explicit. Responsibility exists not only for systems, but for meaning, quality, and appropriate use.
- Quality is measured. Information is held to standards, with consequences when those standards are not met.
- Context is preserved. Information carries provenance, intent, access rules, and lifecycle definition.
- Flows are designed. Creation, validation, distribution, and retention follow intentional patterns.
- Literacy is cultivated. People throughout the organisation can interpret, challenge, and act on information.
- Learning is embedded. Decisions are reviewed against outcomes. Assumptions are tested. Capability compounds.
None of this requires exotic technology.
It requires recognising information for what it has become: a core production process.
The choice
Every organisation now faces a structural choice.
One path continues treating information as a by-product — something that accumulates, is queried when needed, and remains largely unmanaged. This path leads to fragility, delayed decisions, disappointing AI initiatives, and gradual loss of relevance.
The other path treats information as a discipline, with the same rigour applied to finance, operations, or strategy. This path requires organisational design, governance, and skill development. It produces decisions grounded in reality and organisations capable of learning faster than their environment changes.
The revolution already happened.
Information is now the primary raw material of value creation.
The only question is whether organisations continue to treat it as exhaust —
or design themselves to produce it deliberately.