Anthony Alebiosu
The System Architect
← All ideas

Ideas / Information / Working thesis

Information, not data, changes behaviour

A signal only matters when it is meaningful, timely and connected to a decision.

Question

Why can a system collect large amounts of data and still make poor decisions?

Current position

Data becomes operationally useful when it is interpreted as information in a context and connected to an action. More data does not automatically produce better understanding.

Observation

A dashboard can report a number without defining its denominator, time window or relationship to a decision. A customer event can exist in one platform but fail to connect to the customer or application state that gives it meaning. In both cases, data is present while the decision-relevant signal remains incomplete.

Hypothesis

Decision quality depends not only on data availability, but also on semantic clarity, identity, timing, provenance, uncertainty and the mechanism that uses the signal.

Model

A practical information chain is: event or observation → identity and context → interpretation → decision rule or judgement → action → outcome → feedback. Each transition can lose meaning or introduce delay.

Example

Suppose an acquisition report counts app installs while the lending team needs to know which campaign leads to completed loans. An install is a real event, but it is not the outcome the business is trying to optimise. Connecting identifiers and defining funnel transitions can make the data relevant to the decision—while exposing missing identity links and platform coverage gaps.

Limitations

The distinction between data and information is context-dependent and has multiple formal treatments. This note offers a practical systems framing rather than claiming a universal philosophical definition. Information can be misleading, incomplete or wrong.

Implication

Design measurement around the decision first. Define what must be known, by whom, at what time, with what confidence, and what action follows. Then design events, identifiers, data models and reporting around that requirement.

Open question

How should systems communicate uncertainty and missing information so that decision-makers do not mistake a precise-looking metric for reliable knowledge?

← All ideas