The Ambiguity Tax

A pattern keeps showing up in this week’s conversations.

The construction leaders moving fastest aren’t the ones with the best tools. They’re the ones who’ve made the decision to stop tolerating ambiguity.

That’s a strange thing to say in 2026. The industry has spent years investing in software, dashboards, integrations — and most of those investments matter. But what I keep noticing is that the difference between teams pulling ahead and teams stalling isn’t really about which tools they use. It’s about whether they’ve eliminated the ambiguity that the tools are supposed to help them manage.

Where the Ambiguity Lives

It shows up in three places.

Ambiguity about who owns the data. On most projects, no single role has clear authority over the project’s information layer. The GC has some of it. The owner has some of it. The subs have some of it. None of them have all of it, and the gaps are where decisions go to die.

Ambiguity about who has authority to act. Last week’s Field Notes covered this directly. When a PM carries the responsibility but not the decision rights, the project pays the cost in delay. That gap is everywhere, and it shows up most painfully at the moments when speed matters most.

Ambiguity about what “ready” actually means. Most schedules treat readiness as a binary — the next phase starts because the calendar says so. The actual readiness state of the team, the materials, the documentation, the prerequisites — all of that tends to get assumed rather than verified. The result is a slip here, a rework there, a margin point eroded over six months.

None of these are dramatic failures. They’re quiet ones. They don’t show up on the balance sheet under their real name.

What Military Operations Get Right

Veterans I’ve talked to on the show recognize this pattern instantly.

In military operations, ambiguity gets treated as a failure state — something to design out of the system before it costs you something. Pre-mission briefs, rehearsals, defined commander’s intent, explicit handoff protocols. These aren’t bureaucracy. They’re the deliberate removal of ambiguity from the system before contact.

The construction industry has learned to live with ambiguity. To manage around it. To treat it as part of the job. The phrase “we’ll figure it out” has been normalized in a way that would be unthinkable in operations where the cost of figuring it out mid-execution is too high.

That phrase isn’t a sign of resourcefulness. It’s a tax. It just doesn’t show up on the balance sheet under that name either.

The Discipline Problem

Here’s the part that gets uncomfortable.

The teams pulling ahead are doing the harder thing. They’re naming the ambiguity and removing it. That doesn’t require new technology. It requires discipline — the willingness to ask who actually owns this and not move on until there’s an answer. The willingness to define ready with criteria, not vibes. The willingness to make implicit authority explicit.

That’s not a tools problem. It’s a discipline problem.

Tools help once the discipline is there. They reinforce it. They don’t create it. A platform that surfaces project data is only useful when someone has decided who is responsible for acting on it. A workflow that defines handoffs is only useful when the team has agreed that handoffs require verification, not assumption.

The teams investing in their discipline first and their tools second are the ones pulling ahead. The teams doing it the other way around tend to end up with more software and the same problems.

That’s the pattern this week.

---

Field Notes No. 03 lands next week.