The Velocity of Truth

Decision latency is the gap between when a truth becomes available and when anyone acts on it. Most organizations are running at enormous decision latency and not tracking it. The cost is real. It just doesn't appear on any balance sheet.

There is a type of organizational expense that doesn't appear on any balance sheet. It accrues daily, compounds across every function, and is directly measurable in the outcomes it prevents, but because it lives in the gap between what an organization knows and what it does with what it knows, it never gets named as a line item.

Decision latency. The time between when a truth becomes available and when anyone acts on it.

Most organizations are running with enormous decision latency and not tracking it. Someone on the product team has been watching a user behavior pattern for six weeks that contradicts the roadmap assumptions. A manager has known for two months that a team member is a flight risk: not guessing, knowing, based on real signals. A VP has read the early-stage indicators of a market shift that should change the Q3 plan. In each case, the information exists. The organization is paying for it. And it is sitting somewhere in the system, waiting for the moment when surfacing it feels worth the cost.

Information has a shelf life. The earlier a truth reaches the people who can act on it, the more options they have and the lower the cost of those options. The product team that learns in week two that a roadmap assumption is wrong has a menu of adjustments available. The same team learning it in week eight has a smaller menu and higher costs. Every hour a truth sits idle — known but not acted on, surfaced but not escalated, visible but not named — is an hour of compounding cost. The organization pays for knowing something it isn't using.

What keeps information from traveling at speed is rarely technical. Most organizations have adequate channels for information to move. What slows it down is the calculation people make about the social cost of being the one who surfaces it.

The calculation runs like this: the person who knows a difficult truth has to answer a question before they act on it. Not whether the information is accurate, or whether it matters, or what the right response is. The prior question: what happens to the person who surfaces this?

If the answer — based on everything they have observed about this organization — is that the messenger gets blamed, that being the bearer of bad news creates association with the news itself, that raising something that implicates a senior person puts you at risk, then the rational choice is to wait. To let the situation develop until it reaches someone else first. Or until the moment has passed. Or until the cost of not surfacing it exceeds the social cost of surfacing it.

This is not a morale problem. It is a decision latency problem.

The information that an organization most needs to act on is almost always the information that is most costly to surface. The organizational data that would change a decision is held by someone who has concluded that changing the decision is not worth what it will cost them to bring it up.

The result is an organization that makes decisions on incomplete information, not because the information doesn't exist, but because it doesn't travel. The decision gets made. The person who knew something relevant watches it get made. They note the result, file it under evidence of how the system works, and adjust their future behavior accordingly. The next time they know something relevant, the calculation starts a step lower.

The practical consequence of high decision latency is that the organization learns slowly. Not because the people in it are slow learners, but because the feedback loop — from consequence to understanding to adjusted action — gets interrupted at the point where the truth has to travel from the person who holds it to the person who can do something with it. An organization running at high latency makes the same mistakes across cycles because the corrections don't move fast enough to land before the next version of the mistake is already in motion.

The fix is not a better information system. It is an environment where surfacing truth is genuinely less costly than holding it. That is a leadership behavior problem, not a process problem.

Leaders who demonstrate that they can receive difficult information — that the messenger is not blamed, that the truth doesn't create association with the problem, that early signals are rewarded rather than punished — are not just managing culture. They are directly reducing decision latency. They are making the information flow faster.

The velocity of truth in an organization is a leadership output. It is the cumulative product of every interaction where someone decided, based on evidence, that it was safe enough to say the thing early. Or decided it wasn't.