Information Fog
Critical information exists but can't be found, isn't shared, or decays faster than it's captured.
Critical information exists but can't be found, isn't shared, or decays faster than it's captured. Decisions get made on incomplete or stale information.
Recognition signals
- Key decisions are buried in email threads that nobody can find. The decision was made, but reconstructing who decided what, when, and on what basis requires archaeology through a hundred-message thread.
- Context-switching cost from unmanaged information flow. Every new email, message, or meeting interrupts focus. The information architecture doesn't distinguish between "needs your action" and "for your awareness" — so everything competes for attention equally.
- Thread drift — conversations change topic mid-thread and decisions get lost in the noise. A thread that started as a vendor status update ends with a scope decision buried at message forty-seven.
- Vendor meetings have no documentation discipline. Decisions are made verbally, actions are agreed in principle, but nobody writes them down. Three weeks later, "I thought we agreed..." becomes the opening line of a dispute.
- "I thought we agreed..." disputes could be resolved by checking the record — but the record doesn't exist or can't be found. The absence of retrievable decisions creates ambiguity that compounds over time.
Structural cause
Why this happens
Information management is treated as admin, not governance. Nobody owns the information architecture. Communication tools — email, chat, meetings — are designed for transmission, not retrieval.
The fog isn't caused by too little information. It's caused by too much undifferentiated information. When every email is marked urgent, nothing is. When every meeting is mandatory, none of them produce decisions. The signal-to-noise ratio collapses, and people compensate by tuning out — which makes the fog worse.
The structural fix isn't more documentation. It's better information architecture: clear conventions for what goes where, what needs action vs awareness, and how decisions get recorded and retrieved. Without architecture, every new piece of information adds to the fog rather than clearing it.
Risk mapping
| Risk | Description |
|---|---|
| K1 | Productivity tax — context-switching from unmanaged information flow |
| K2 | Findability — critical information exists but can't be retrieved |
| K4 | Audit gap — decisions not recorded or recordings not retrievable |
| C5 | Communication decay — CC culture replaces clear, directed communication |
Self-assessment
When to worry
- Key decisions are buried in email threads nobody can find
- Vendor meetings produce no written record of decisions or actions
- "I thought we agreed..." disputes are recurring
- Context-switching cost is visibly eroding team productivity
When you're OK
- Decisions are recorded in a single searchable location
- Meeting records capture decisions and actions within 24 hours
- Communication channels are differentiated — action vs awareness
Related reading
- Email triage — a structured system for managing information flow
- Incentive Inversion — hoarding makes fog worse, fog makes hoarding more rational
- Transition Cliff — knowledge doesn't transfer because it was never captured
The fog is not too little information — it's too much undifferentiated information with no governance effect.
A programme health check assesses decision capture, communication channels, and information architecture. 10fifteen — programme governance assessments.