Why a Faster Decision Is Usually a Better One

In short: we treat a slower, more careful decision as the safer, better one. For the everyday operational calls that make up most of an organisation's work, that instinct is usually wrong. Time is part of a decision's quality, not separate from it; past a point, more deliberation makes the outcome worse, not better; and the risk we instinctively attach to an imperfect decision is usually far larger than the real cost of making one. Speed isn't the opposite of quality. For operational decisions, it's part of it.

This is one thread in the fuller picture of why capable teams get bogged down — and the same pattern shows up across local government too, covered in the Council Operational Performance hub.

The assumption hiding in "let's take our time to get this right"

We rarely say it out loud, but a belief runs underneath most organisations: that a decision improves the longer you think about it. More analysis, more consultation, another round of sign-off — each feels like it's adding rigour and lowering risk. So "we took our time to get it right" is said with pride, and "that was a rushed decision" is an accusation. Both assume the same thing: that time and quality move in the same direction. For operational decisions, they mostly don't.

Time is part of the decision, not a cost you pay for quality

A decision's value isn't fixed while you deliberate — it decays. A supplier approved this week and the same supplier approved in six weeks are not one decision at two speeds; they're two different outcomes. The customer waited. The opportunity moved. The team built workarounds to cope with the gap. Delay isn't a neutral price you pay to buy certainty — it's a subtraction from the value of whatever you eventually land on. A good decision delivered late is often just a worse decision. Timeliness is one of the things that makes a decision good, sitting right alongside "was it the correct call" — not something you trade away to get there.

Deliberation has diminishing — then negative — returns

More thinking stops improving a decision surprisingly early. The first hour on a problem does most of the work; the fifth adds a little; the fifth meeting about it adds almost nothing but calendar time and the feeling of diligence. Past that point you aren't de-risking the decision — you're paying for it in delay, and often making it worse, as more voices, more caveats and more competing preferences crowd in. "We need more information" is sometimes true. Just as often, it's the most defensible way available to not decide.

The risk you feel is bigger than the risk you face

Here's the point that quietly undoes most over-caution: the dread attached to an imperfect decision is wildly out of proportion to what being wrong would actually cost. The imagined downside is vivid and immediate — the mistake, the exposure, the awkward conversation. The real downside, for most operational decisions, is far more modest: some rework, a customer mildly inconvenienced, a result that lands at 80% and gets corrected next cycle. Many of these calls do touch the customer directly — but "touches the customer" and "carries the catastrophe the dread implies" are not the same thing. The actual material and reputational cost of a sound-but-imperfect decision is usually small and recoverable. The fear attached to it is not.

Why the gap? Because being wrong is visible and personal — it attaches to whoever made the call — while the cost of being slow is diffuse and ownerless, spread thinly across the customer, the team and the organisation with no single name on it. So people rationally over-insure against the vivid personal risk (being blamed) and under-weight the real but unattributed one (the drag of delay). Caution gets scaled to an imagined worst case, not to the risk actually in front of them.

The one caveat: match the caution to the decision

None of this argues for snap judgements on everything — the opposite. It argues for matching the caution to the real risk. Genuinely consequential calls — a major capital commitment, a structural change, a long-term partnership, where the material and reputational stakes really are large — deserve their time, and rushing them is its own failure. The problem isn't that organisations deliberate. It's that they apply that same weight to operational-grade decisions, by default, thousands of times a week, where the real risk is a fraction of the one they feel. That's where the drag lives.

That's why decision friction — the resistance a system puts in the way of reaching a decision — is a cost, not a safeguard. When the systems around a capable team quietly reward slow-and-defensible over fast-and-sound, the team isn't being careful. It's being slowed, on exactly the calls where speed was part of the right answer.

Want a read on whether your systems reward speed or quietly punish it? The Friction Factor survey is a fast, free first look.