The cost of delay isn’t time. It’s drift.

A decision gets pushed to next month because the team wants one more round of input.

On paper, that sounds sensible. Nobody wants to move too fast on segment focus, pricing policy, a senior hire, or a product commitment tied to revenue.

The issue is not ignored. It is deferred. The calendar absorbs the delay and the business carries on.

The Cost of Delay Isn’t Time — It’s Drift

That is where teams misread what delay actually costs. When leadership groups talk about slow decisions, they often describe the problem in terms of elapsed time. A call took three weeks instead of three days. A discussion slipped past the board meeting. A hiring decision rolled into the following quarter. Time is visible, so it becomes the default measure. But in most B2B SaaS businesses, the real cost of delay is not the number of days that pass. It is the drift that sets in while the issue remains unresolved.

Drift Turns One Decision Into Many Local Ones

Drift is what happens when the organisation continues to move without a settled operating position. Work does not stop. People interpret the likely direction, hedge their bets, protect their own function, and make local decisions in the absence of a clear whole-business call. By the time leadership returns to the issue, the company is often dealing with a larger problem than the original decision ever presented.

A familiar example is a debate over whether to keep supporting a demanding customer segment that generates decent revenue but creates disproportionate product and service strain. The leadership team knows the issue matters. Sales sees value in the segment. Product and support are carrying the complexity. Customer Success is handling escalations and expectation management. Finance is starting to question the quality of the revenue. Because the segment is not obviously unprofitable and not obviously strategic, the team keeps postponing the decision while gathering more information.

While Leadership Waits, the Business Commits Anyway

During that period, drift takes hold. Sales continue selling into the segment because nothing has been explicitly restricted. Product keeps making small concessions to avoid acute customer pain. Customer Success develops workarounds to preserve relationships. Support absorbs more edge-case demand. Marketing does not know whether to qualify these accounts harder or continue current targeting. By the time the leadership team finally makes a call, the business has deepened its commitment through dozens of local decisions made in the vacuum.

That is why delay is so expensive. The organisation rarely waits in place. It adapts around uncertainty. Those adaptations are usually rational at a local level. A salesperson wants to close the quarter. A product manager wants to reduce immediate noise. A CSM wants to save a customer relationship. A founder wants to preserve optionality. The problem is that these rational local moves can combine into strategic incoherence.

Why Drift Is Hard to See — and Easy to Underestimate

Most teams underestimate this because drift does not arrive as a headline event. It arrives as rework, inconsistent messaging, duplicated effort, growing exception handling, and a creeping loss of trust in whether leadership decisions actually stick. People begin to assume that the current position is provisional, so they keep options open. Once that becomes cultural, even relatively simple decisions start taking on more weight because everyone has seen how easily clarity dissolves.

Another reason delay is misread is that leaders often compare the cost of waiting only against the cost of being wrong. They ask whether it would be irresponsible to decide with imperfect information. That is a fair question. What they often fail to ask is what the business is already paying for continued ambiguity. In commercial environments, that cost can be substantial. Deals are negotiated against uncertain policy. Product work is reprioritised informally. Customer promises are softened or stretched. Forecasts become harder to trust because the operational assumptions beneath them keep shifting.

The issue is particularly acute in Series A and B businesses because the operating system is still being formed. Larger companies can sometimes absorb a period of ambiguity through process depth, managerial layers, or established policy. Smaller scaling businesses often cannot. A few weeks of drift at the leadership level can change frontline behaviour fast, and those behavioural shifts are harder to unwind than many founders expect.

Delay Isn’t Neutral — It Actively Shapes Behaviour

What people usually get wrong is assuming that delay preserves neutrality. It rarely does. Delay is an active condition. It creates incentives, behaviours, and interpretations. It encourages functions to optimise for self-protection because the whole-business frame is not settled. Over time, that makes the eventual decision harder, because each function has accumulated more sunk cost in its own local response.

Decide Based on the Cost of Ambiguity, Not Just Risk

A more useful way to think about decision speed is not speed for its own sake. It is speed relative to the cost of drift. Some decisions should take time because the downside of haste is real. Others should be made faster because the organisation is already paying to live in ambiguity. The right question is not simply how quickly can we decide. It is what happens to the business while we do not.

Take a hiring example. A company is debating whether to add a senior implementation leader after several strained enterprise rollouts. The leadership team is not convinced the volume justifies the hire. Fair enough. But while the decision drifts, solutions engineers are doing implementation design work, CSMs are absorbing project coordination, product is fielding escalations that should have been handled elsewhere, and sales is moderating enterprise ambition because delivery confidence is low. The cost of delay is not just one unfilled role. It is the distortion of multiple other roles around the gap.

The same pattern shows up in roadmap decisions, segment choices, renewal strategy, and pricing exceptions. The business tells itself it is being careful. In practice, it is often distributing the cost of indecision across teams that are already carrying enough. Because that cost is fragmented, leadership underestimates it.

The remedy is not reckless decisiveness. It is to make the hidden cost visible early. When an issue is live, someone needs to ask a harder question than whether more information would help. What is the current ambiguity causing in the business right now. Which teams are creating workarounds. What promises are being made in the gap. What precedent is being created through informal behaviour. What would happen if we left this unresolved for another month. Those questions shift the frame from theoretical caution to operating reality.

This is also where a written decision frame helps. It gives the team something concrete to assess. Are the remaining unknowns material enough to justify delay. Or are they simply the normal uncertainties that accompany any executive call. Once the decision is made explicit on paper, it becomes easier to judge whether the business is waiting for essential input or hiding inside more discussion.

Good leadership teams do not aim to eliminate uncertainty before deciding. They aim to reduce unnecessary drift while making the best judgement available. That requires a more disciplined view of time. Calendar time is only one part of the equation. Organisational movement under ambiguity is the more important one.

The practical takeaway is to stop treating delay as empty space. It is not empty. It fills up quickly with assumptions, exceptions, and local coping mechanisms. When a decision remains open, the business is still making one, just in a less coherent way. The more important question is whether leadership wants that informal version to be the one the company ends up living with.

Need help with a decision? Get in touch now.