Information Isn’t What You Know

Last Friday’s standalone made the case that construction generates a lot of reports — not a lot of information. The natural follow-up: if reports aren’t information, what is?

Information that drives action shares three properties. It names what needs to be decided. It names who’s responsible for deciding. And it names by when.

Without those three, the artifact is producing awareness. Awareness is comfortable. It distributes broadly. It makes everyone feel informed. But it doesn’t move the project forward, because no one is specifically required to act on a specific question by a specific time.

What, Who, When

Each of those three properties does specific work.

What needs to be decided. A status update can be accurate without surfacing the decision the project actually needs. Steel is two weeks behind is observation. Steel is two weeks behind. We need to approve the alternate supplier by Friday or it becomes a three-week delay is information. The first describes a state. The second names the inflection point.

Who’s responsible for deciding. Information that lands on ten desks often gets acted on by zero. Each recipient assumes someone else is closer to the issue, has more context, or has more authority. The CC line distributes awareness while diffusing ownership. Information designed for action names exactly one decision-maker — and the document itself signals to the other recipients that they’re being informed, not asked to act.

By when. Information without a window of action is information that can be acted on later. Later is where most decisions go to die. The window doesn’t have to be tight to be useful, but it does have to exist. The decision-maker needs to know whether they’re acting in the next twenty-four hours, the next two weeks, or before the next quarterly review.

Strip any of those three out and the artifact stops being information. It becomes something else — usually awareness, sometimes documentation.

Why Awareness Feels Like Information

The reason this pattern persists isn’t that operators don’t recognize the problem. It’s that awareness is structurally comfortable to produce and consume.

Producers feel like they communicated. They sent the report, attached the dashboard, ran the meeting. The act of distribution feels like the job got done. The system records that information moved. The producer’s responsibility is discharged.

Receivers feel like they were informed. They got the update. They know the state of things. They can speak credibly about the project in the next meeting. Their awareness is current.

What’s missing in both cases is the moment of commitment — the producer saying this person needs to do this thing by this date, and the receiver saying I own that decision. Awareness is everyone’s comfortable middle ground. Information forces a position.

That’s why “information overload” is usually a misdiagnosis. Most leaders aren’t overwhelmed by information. They’re overwhelmed by awareness — the comprehensive coverage they receive every week, none of which specifically requires them to do anything in particular. Real information tends to be rare enough that when it lands clearly, it’s a relief.

Two Models of Information

Military intel is built for action by design. Every intel product names a specific consumer, a specific decision, and a specific time horizon. Intel that doesn’t meet those criteria isn’t intel — it’s situational awareness, which serves a different purpose and goes to different people.

The architecture is deliberate. Intel that goes to a commander’s desk is filtered. Other people higher and lower in the chain see different products built for their decisions. The same underlying data gets shaped into different artifacts depending on who needs to act on it and what they need to act on. Intel products carry assessments, recommended courses of action, confidence levels, and explicit time horizons. The work of making information actionable is the work itself.

Construction often inverts this. The data exists in one place, gets pulled into reports designed for broad distribution, and goes to everyone who might find it relevant. The architecture optimizes for coverage, not action. The same dashboard goes to the executive, the PM, the superintendent, and the owner — each of whom needs a different decision surfaced. The result is a document that informs everyone and obligates no one.

What the Teams Pulling Ahead Are Doing

Three patterns keep showing up among teams that have closed this gap.

They design each output around a specific decision. Before a recurring report is built, the team answers: what decision is this document supposed to enable, and who’s making it? The structure of the document gets shaped by that answer. Coverage gets sacrificed for clarity. Some recipients receive less than they used to — but what they receive is what they can act on.

They name the owner of the decision in the document itself. Not in the CC line. Not in an implicit understanding. The artifact names who’s responsible for making the call. That naming does two things at once: it signals to the named person that they own the decision, and it signals to everyone else that they’re being kept informed, not asked to act.

They name the window in which the decision is still actionable. Either explicitly — decision needed by Friday EOB — or structurally, with the document arriving on a cadence that maps to a known decision rhythm. The window is what converts the information from good to know into now is when you act.

That’s not a documentation problem at the individual level. It’s an infrastructure one — the same shift this series keeps returning to. Build the system that produces decision-grade artifacts, and the action follows. Build the system that produces coverage, and you get a lot of awareness without much movement.

Information isn’t what you know. It’s what someone can act on.

If it doesn’t name what, who, and when — it’s awareness, not information.

---

Field Notes No. 05 — The Handoff — was the integration moment of the series. No. 07 lands next Wednesday and looks at the gap between information and action.