Every company has a financial tax rate they can name to the decimal. Almost none of them can name their decision latency. Decision latency is the time between when a question surfaces and when a committed answer exists. Not explored. Not discussed. Committed. And in growth-stage companies, it is quietly the most expensive line item that will never show up on a P&L.

Here is the pattern nobody talks about. Between $3M and $20M revenue, the number of decisions that need to be made explodes, but the number of people who feel authorized to make them stays the same. Usually the same one or two people. So every question funnels to the top of the house, queues behind everything else already sitting there, and waits. Meanwhile the team learns something corrosive: asking is slower than guessing. So they stop asking. They stop flagging. They start shipping workarounds and calling them alignment.

That is the tax. Not the delay itself, but the adaptation to the delay.

Consider what a two-week decision latency actually costs. A pricing question sits for two weeks, so packaging waits, so the campaign brief waits, so the launch slides a month. A key hire discussion stalls for two weeks and your strongest operator takes a competitor call because she cannot see a future being built. None of these show up in a postmortem, because none of them look like failures. They look like a normal quarter.

The compounding math is brutal. If a company makes a few hundred meaningful decisions a year, and each one waits an average of ten business days, the organization is not moving at the speed of its market. It is moving at the speed of its calendar access to you.

So why does this happen? Three structural causes, in order of frequency.

First, decision rights are undefined. Most teams have job descriptions that describe what people own, but never what people decide. The two are not the same. When nobody is sure who the decider is, every decision becomes a consensus process, and consensus is the most expensive decision-making apparatus ever built.

Second, the founder has confused involvement with control. This one lands hard for Founder-CEOs, because in the early days being the decider on everything was the correct strategy. You were the product. You were the sales team. You were the quality bar. But the behaviors that got the company to $3M are the exact behaviors that cap it at $20M. If every meaningful decision still routes through you, you have not built a company. You have built a queue.

Third, decisions have no deadline. A decision with no deadline is not a decision, it is a discussion topic. And discussions can live forever.

Here is the fix, and it is not another meeting cadence. It is a decision rights map. One page. Three columns. For each domain of the company: who decides, who is consulted before the call, who is informed after it. Decides means one name. Not a committee. One accountable human being whose call it is. Consulted means input is genuinely sought before the decision. Informed means they hear the outcome, not the debate.

Then add a decision SLA. Not every decision deserves the same clock. Sort them into three speeds. Type one, reversible and cheap, decide within 24 hours and let the decider go alone. Type two, reversible but expensive, decide within a week with consultation. Type three, hard or impossible to reverse, take two weeks max, involve the full brain trust, and decide on a named date. The discipline is not deciding fast. It is knowing which speed each decision deserves before the debate starts.

Then do the piece most leaders skip. Sunset the queue. If a decision has been open more than 30 days, either it does not matter, in which case kill it, or it matters and the delay is already costing you, in which case force the date.

Before any of this, ask the question that actually determines your trajectory: what are we optimizing FOR? Because cutting decision latency is not about speed for its own sake. Speed without clarity just lets you thrash faster. The point of decision discipline is that it buys back the scarcest resource a Founder-CEO has. The cognitive space to think about the only decisions that genuinely need you. The ones no one else can make. Strategy, capital, key people, and who you are becoming as a company.

Audit it this week. Ask your team one question: what decision are you currently waiting on, and who is the decider? If the answers make you uncomfortable, good. That discomfort is the first honest data you have collected about your operating system in a while.