Ask a leadership team how long it takes to make a decision and the answer is usually framed in hours. Ask how long the last pricing exception, supplier choice or hire took to move from request to answer, and the number is more often measured in weeks. The gap between those two answers is decision latency, and it tends to widen as a business grows.

Decision latency is the elapsed time between a decision being needed and a decision being made. It is not the same as deliberation. A well-run discussion that weighs evidence and emerges with a clear answer is an investment, and the discipline to think before committing is a strength. Latency is the interval that adds nothing: the request sitting in an inbox, the meeting postponed because a key attendee is travelling, the third review of a choice that was already clear after the first. It is an operating cost that rarely appears on any management report, and it quietly erodes margin, morale and responsiveness.

What decision latency is, and what it is not

The distinction matters because leaders often defend slow decisions as evidence of rigour. Sometimes they are right. Choosing a new core system, exiting a market or appointing a senior hire are choices worth taking time over. But the same caution is frequently applied to decisions that could be made and unmade within a week.

Consider the routine decisions that fill a growing company's calendar:

  • Hiring approvals, where a manager waits weeks for sign-off on a role that has already been budgeted.
  • Pricing exceptions, where a salesperson cannot offer a small concession without escalating to a director.
  • Supplier selection, where a comparison of three credible quotes is passed through two committees.
  • Customer escalations, where a service issue waits for a senior leader to return from a trip.

In each case, the cost of being wrong is modest and the cost of being slow is not. A company that requires the same three signatures for a modest pricing exception as for a new market entry is not being careful. It is applying a governance standard designed for irreversible choices to a decision that could be reversed by Friday.

Why growing businesses slow down

Latency is rarely caused by one bad process. It accumulates as the business adds people, products and customers, and each addition brings another stakeholder with a legitimate interest in the outcome.

The first cause is unclear decision rights. When nobody is sure who owns a decision, the safest course is to involve everyone, and the committee becomes the default owner. The second is meeting-heavy governance. A weekly leadership forum designed to review strategy drifts into approving stationery and resolving scheduling conflicts because it is the only room where everyone is present. The third is risk aversion. As a business gets larger, the perceived cost of a visible mistake rises, and escalation becomes a way of sharing accountability rather than resolving a question.

Underneath these sits a structural issue: the founder or senior team remains the final arbiter for decisions that the organisation is now large enough to make without them. Each escalation is individually reasonable. Collectively, they turn the calendar of two or three people into the throughput limit of the entire business.

The compounding cost of waiting

Slow decisions do not produce a single visible loss. They compound.

Revenue arrives late when a pricing decision delays a proposal. Teams sit idle waiting for a scope to be confirmed, then work in a compressed burst to recover the time. Analysis is duplicated as each new reviewer commissions a fresh version of a case that was already sound. Accountability thins, because a decision made by a group belongs to nobody in particular. Customers and competitors move on while the business is still assembling its response.

There is a cultural cost too. People learn quickly whether proposing something leads to an answer or a void. In organisations where the void is common, the quiet adaptation is to stop proposing, and initiative drains away without any decision ever being taken to discourage it.

Designing decision rights and escalation rules

The remedy is not to decide everything faster. It is to decide deliberately how each type of decision should be made.

A useful starting point is to sort decisions along three questions: how easily can this be undone, how much does it matter, and how quickly does the answer lose value? A reversible, modest-impact choice with a short shelf life — a discount on a single order, a temporary change to a delivery schedule — should be made close to the work, by the person who understands it. A reversible but high-impact choice should be made quickly and then monitored, because the cost of being wrong is recoverable and the cost of being slow is not. An irreversible choice with modest impact is rare and can be delegated within clear parameters. An irreversible, high-impact choice deserves genuine deliberation and senior involvement, and should be scheduled rather than left to find its moment.

Each category then needs a single named owner. Not a function, not a committee: a person. Alongside ownership sit escalation thresholds expressed in concrete terms, whether a spend limit, a discount ceiling, a headcount number or a defined set of customer circumstances. Below the threshold, the decision is made and recorded. Above it, the decision escalates on a stated timetable rather than at the convenience of the most senior attendee.

Operating routines that keep decisions moving

  • A decision log. A simple record of what was decided, by whom, when it takes effect and what would trigger a review. It ends the cycle of relitigating settled questions.
  • Service-level expectations for common approvals. A stated turnaround for pricing exceptions, purchase approvals or contract sign-offs, with an owner accountable for meeting it.
  • Meeting cadences matched to decision types. Short, frequent operational sessions for reversible choices; less frequent, longer sessions for the irreversible ones.
  • Periodic reviews of where delays recur. Sampling recent decisions and asking how long each took from need to answer reveals the bottlenecks that no process map shows.

None of these routines requires new software or a reorganisation. They require a decision about how decisions will be made, and the consistency to hold to it.

Decision speed is a design choice

It is tempting to explain slow decision-making as a personality trait, a feature of the founder, the industry or the management team's temperament. It is more useful to treat it as a design problem. Organisations get the decision speed their structures, thresholds and meeting habits are built to produce.

The responsiveness that carried a business through its early years was rarely the result of formal governance. It came from proximity: the people who understood a problem were also the people allowed to solve it. Growth inevitably separates those two things, but it does not have to sever them. Clear decision rights, proportionate governance and explicit escalation rules allow a larger business to keep something of that early speed, and to stop paying for delay it never chose.

← PreviousBack to Articles