Information Enables Action. It Doesn’t Compel It.

Last week’s column made the case that information has to name what, who, and when to be actionable. The argument’s natural test: if information meets that bar, does action follow?

Not always.

Imagine the perfect report. Recipient filtered to one decision-maker. Deadline named. Required decision surfaced clearly. Does the project still slip? Often. The information was there. The decision was clear. The action waited.

That’s the gap worth naming. Information that meets the No. 06 bar enables action — but it doesn’t compel it. Between the moment a decision-maker receives clean information and the moment they act, there’s a second gap that no amount of better reporting will close.

The Structure of the Gap

The gap between information and action has a shape. It’s not random. It’s predictable.

A decision-maker receives clean information. They have authority. The deadline is real. But the act of deciding requires accepting that the available information will never be complete enough to guarantee the right call. So they look for more.

They ask for one additional data point. They schedule a follow-up meeting. They escalate to share the weight of being wrong. They request one more pass from the team. They wait for the next status review. Each step looks rational in isolation. Each one delays the action by a day, a week, a phase.

Collectively, these steps compound into the kind of delay that doesn’t show up on a Gantt chart but accumulates in the margin. The schedule didn’t slip because of a single bad decision. It slipped because dozens of clear decisions waited for clarity that was already present.

The OODA Loop

Military doctrine has a name for the cycle this gap interrupts. The OODA loop — Observe, Orient, Decide, Act — was articulated by Colonel John Boyd to describe how operators move from awareness to action under pressure.

The model’s central insight: the cycle itself is the unit of operational tempo. Teams that cycle faster don’t win because they have better information. They win because they spend less time inside the loop. By the time a slower opponent finishes orienting, the faster team has already acted, observed the result, and started the next cycle.

The loop’s bottleneck is rarely at Observe. The information is usually available. The bottleneck is usually at Decide — specifically at the transition from Decide to Act. That’s where the willingness to commit on incomplete certainty either happens or doesn’t.

Construction’s loop often stalls there. The information was clean. The owner was clear. The deadline was named. And the project paid the cost of analysis that didn’t change the answer.

Why the Gap Persists

The gap persists not because operators don’t recognize it, but because the structure of construction often rewards a certain kind of caution.

The cost of acting on incomplete information is visible. If the decision turns out wrong, the consequence has a name — a change order, a rework, a claim, a margin loss attributed to a specific call. The cost of not acting in time is diffuse. It distributes across the schedule. It doesn’t have a single owner. No one points at a meeting two months later and says, that delay started when we waited a day to make the call.

That asymmetry makes hesitation feel rational. A decision-maker can be blamed for a wrong call. They can rarely be blamed for a slow one. Especially in a contractually adversarial environment where every party is watching for liability, the safest move often feels like waiting.

The teams pulling ahead have changed that incentive. Hesitation has a visible cost. Action on clean information gets rewarded even when the call turns out imperfect. The system signals that correct and slow is worse than good enough and fast.

What the Teams Pulling Ahead Are Doing

Three patterns keep showing up.

They accept that decisions live on incomplete information. The teams that close the gap don’t pretend their information will get more complete in the next twenty-four hours. They accept the level of certainty available and decide. The discipline upstream — the work from No. 06 of designing decision-grade information — gives them confidence that the available information is the right information. The downstream work is just to act on it.

They reduce the friction between knowing and acting. Escalation paths get shorter. Approval chains get clearer. The number of meetings required to confirm what was already in the document gets cut. Speed of decision becomes a tracked operational metric, not a soft cultural value.

They build upstream trust so escalation isn’t required for cover. When a decision-maker has cover from leadership to be wrong occasionally, the calculus changes. The act of deciding becomes the work. Seeking confirmation becomes the exception. That trust doesn’t build by accident — it builds through repeated cycles where leaders honor good decisions made on imperfect information, even when they don’t turn out perfectly.

That’s not a courage problem at the individual level. It’s an infrastructure one — the same shift this series keeps returning to. Build the system that surfaces actionable information, then build the cultural infrastructure that lets people act on it.

Information enables action. It doesn’t compel it.

The gap between the two is where projects are won or lost.

---

Field Notes No. 06 — Information Isn’t What You Know — covered what makes information actionable. No. 08 lands next Wednesday and looks at the cost of being right too late.