Quick Decision Making: When Speed Is the Right Call — and When It Isn't

When Is a Fast Decision the Right Call?

Speed isn't reckless. In the right conditions, it's the only rational choice.

Ask yourself these three questions before you move. Each one tests whether your situation actually calls for speed — or whether the urgency is coming from somewhere else entirely.

The first is reversibility. If you can undo the call without significant cost, the risk of moving quickly is low, and the cost of hesitation is real. Richard's dismissal was technically reversible — he proved it. But it didn't feel that way in the room.

That feeling isn't a condition. It's noise.

The second is delay cost.

When waiting actively worsens your position — a competitor moves, a window closes, a team stalls — the cost of the decision already includes the cost of taking time. Richard's salesperson wasn't going anywhere.

Waiting forty-eight hours costs nothing. The pressure to act came from outside the decision, not from within it.

The third is information maturity. Waiting only makes sense if it produces new information that changes the outcome. In Richard's case, it did — six months later. That information was available earlier, in a quieter conversation he hadn't had before he acted. He didn't wait for it.

Richard met none of the three conditions. He moved anyway. That's not decisiveness. That's the appearance of it.

Three Frameworks That Make Quick Decisions Sound

Speed without structure is just urgency.

Reversible Decisions

The cleanest rule in decision-making is also the most underused.

If the decision is reversible, move fast and correct as you go. If it's irreversible, slow down regardless of the pressure. Jeff Bezos built Amazon's decision culture around this single distinction — Type 1 decisions get deliberate process, Type 2 decisions get speed.

Most organisations apply the same process to both, which means they're either too slow on reversible calls or too fast on irreversible ones. The fix is the distinction, not the speed.

The classification is rarely the problem. The pressure in the room makes every decision feel irreversible — and that feeling is almost never accurate.

Rule-Based Decisions

The fastest decisions are the ones already made.

A pre-committed rule removes deliberation from decisions that recur — the cognitive load lands once, when you set the rule, not every time the situation arises.

Richard had a rule: consistent underperformance plus tracker evidence equals dismissal. The rule wasn't wrong. But it was applied without the judgment the situation required. A pre-committed rule works when the conditions are standardised.

When the situation has variables the rule wasn't designed for — an exceptional performer, an incomplete information picture — the rule needs a human layer on top of it.

The leaders who appear most decisive under pressure aren't thinking faster. They decided earlier.

Capped Downside

When you can't pre-commit, and the decision isn't cleanly reversible, the question becomes: what's the worst outcome if this is wrong?

Netflix green-lit House of Cards in a thirty-minute meeting. It was fast because the downside was defined — one show, one contract, a contained exposure against a potentially category-defining upside.

Most leaders never run this calculation explicitly. They feel the upside, absorb the pressure, and move — without naming what losing actually looks like. That's not a fast decision. That's an unconsidered one. The difference is whether you've looked at the floor before you jumped.

Fast decisions feel reckless when the downside is unlimited. Cap the downside, and speed becomes rational.

If you haven't mapped the worst-case scenario before you move, you haven't capped the downside — you've just ignored it.

Define what losing looks like. Then move.

When Fast Is the Wrong Call

Not every decision rewards speed.

Two conditions make fast decisions genuinely dangerous.

The first is irreversibility combined with high stakes. When a decision can't be undone, and the consequences are significant, deliberate thinking isn't optional — it's the only responsible process.

The pressure to decide quickly in these situations almost always comes from outside the decision itself: a deadline, a room full of people waiting, a sense that hesitation signals weakness. None of those is a reason. They're noise.

The second is missing information that matters.

If waiting twelve hours, or two days, produces data that genuinely changes the call — a conversation with the person most affected, a financial projection, a legal read — then speed is just impatience dressed as confidence.

This is where emotional intelligence does its real work. Not in the decision itself, but in the moment before it.

The capacity to notice which mode a decision actually requires is the skill. Resisting the pressure to collapse that question into urgency is how it shows up under fire. If the information picture feels genuinely incomplete, the article on decision making under uncertainty covers that ground directly.

The Clock and the Room

Richard's dismissal wasn't the mistake. Making the call before the information was in — that was the mistake. A forty-eight-hour pause and one conversation would have changed the outcome. Both were available. Neither happened.

The three conditions aren't a checklist you run after the pressure arrives. They're a question you train yourself to ask the moment a decision lands. Is this reversible? Does delay cost more than error? Does waiting give me anything new?

Most leaders never ask. Not because they don't know to — but because the room is already moving and asking feels like falling behind.

For the wider framework behind every call you make, the Leader's Guide to Decision Making is where to start.

The next time someone puts a decision on your desk and says we need this now — is the clock real, or is it just the room?