The weekly Executive Briefing: insights, books, tools, and media opportunities worth your attention — curated and distilled into 5 minutes.
You have opened the same email four times this week. It asks for a yes or a no, and each time you close it with a note to think about it later. Nothing new has come in. The decision has simply become heavier every time you looked away. Rapid decision making is the fix for exactly this.
That is the case for rapid decision making. Most delayed decisions are not hard, they are unfinished, and the delay does its own damage. Speed beats accuracy under two conditions: the choice can be undone at a reasonable cost, and waiting costs more than a mistake would. When both are true, deciding quickly is the better call.
What Slow Decisions Actually Cost
The price of waiting is rarely written down, which is why it feels free. In fact it has several parts. Other people are stuck until you answer. The option itself may expire. Your own attention stays partly occupied by the open question, which lowers the quality of everything else you are working on.
Against this, the case for waiting is usually that more information will help. Sometimes it will. More often you already hold most of what you will ever learn, and the extra research is a way of postponing the discomfort of being wrong.
The useful comparison is between the cost of an error and the cost of delay, both measured in the same place, such as days lost or money spent. If the error is cheap to fix and the delay is expensive, the maths is already done.
Rapid Decision Making Depends on Reversibility
Every decision sits somewhere between two poles. At one end are choices you can reverse: a price test, a job posting wording, a supplier for one order, a meeting format. At the other are choices you cannot: signing a long lease, hiring a senior person, selling the business, taking on debt.
The mistake is to give both kinds the same amount of deliberation. Reversible choices deserve a quick decision and a way to check afterwards. Irreversible ones deserve real time. Most organisations run these the wrong way round, spending weeks on reversible choices because they are more frequent and feel more visible, and rushing the irreversible ones because a deadline appeared.
Start by asking the plain question: if this turns out wrong, how hard is it to undo? If the answer is a phone call or a week, decide.
A first hire such as a bookkeeper is a choice you can reverse, as bookkeeper vs accountant explains. Two years of study is one you cannot, which is why whether an MBA is worth it deserves the slow process.

The Four Question Filter
When a decision is stalling, four questions sort it quickly.
First, can it be undone, and at what cost? Give the cost a number if you can: hours, money, damage to a relationship.
Second, what does waiting cost per day? A missed deadline, a blocked team, a lost supplier price. If you cannot name a cost, waiting may be fine, and you are free to slow down.
Third, what would change my mind? If you can name the fact that would flip the decision, go and get that one fact. If you cannot name one, more information is not what you are waiting for.
Fourth, who else has to decide? Some decisions stall because they belong to someone else, or because the wrong person holds them. Handing them on is a decision too, and often the fastest.
Answer these in writing, in a few minutes. Two or three of the four will usually point the same way.
Put a Clock on It
A decision without a deadline expands to fill the time you allow. So set one when you start. A rough guide is that a decision should take about as long as its consequence is large and its reversibility is low, and no longer.
For a reversible choice, a few minutes is often enough. For one with a medium cost, a day. For a big one, a fixed date with a fixed process attached. The point is that the end time exists before you begin, and that you decide when it arrives with the information you have. Military strategists built a whole model on this idea, the OODA loop, which treats the speed of the observe, decide and act cycle as an advantage.
Many people find that a rough threshold helps: decide once you have enough to be roughly two-thirds sure. Waiting for near certainty costs more than it returns, because by then the option is often gone. The exact number matters less than agreeing a threshold before you start, so that you are not renegotiating it while under pressure.
Decide the Reversal in Advance
A quick decision is safe when it comes with an exit. Before you commit, write down the signal that would tell you it is failing and the date you will check. If a new hire is not making progress by week six, you will have a conversation. If a price test drops conversion below a set level, you go back.
This is what turns speed into a method rather than a gamble. The decision is fast, and the review is scheduled. Because you know a check is coming, the discomfort of committing shrinks.
It also means that mistakes stay small. A wrong choice caught in two weeks costs two weeks. The same choice left to run because nobody wrote down what failure looked like can cost a year.
Use Defaults for Repeat Decisions
Many decisions you make are the same decision in different clothes. Which requests to accept, when to reply, which vendors to use, how much to spend without asking. Writing a default for each removes the decision from your day.
A default is a rule you set once, when you are calm, and follow when you are busy. It is the reason experienced people seem to decide instantly. They have already decided, in advance, what they do in a familiar situation. If you find yourself worn out by choices by mid-afternoon, decision fatigue is the mechanism, and defaults are the cheapest remedy. The best-known study of the effect looked at rulings across a working day, Extraneous factors in judicial decisions.

When to Slow Down
Speed is a tool with limits. Slow down when the choice cannot be undone, when the downside is severe even if unlikely, when you are angry, frightened or exhausted, or when you are being pushed to decide by someone who benefits from your haste.
Artificial urgency is a sales technique as much as a management one. A deadline invented by the other side is a reason to look harder, not faster.
For the large, irreversible choices, the process in structured decision making is the right tool. It is deliberately slow, and it is meant for the small number of decisions that deserve it. Rapid decision making and structured decision making cover different ends of the same range, and the skill is in sorting each choice to the right end. If you enjoy reading around the subject, the best books on decision making is a good next step.
A Rule for Tomorrow Morning
Take the decision you have been avoiding. Answer the four questions on paper. Set a time limit of one hour. Write the signal that would tell you it was wrong. Then decide, and send the reply.

Written by
Victor Lanza
Editor of The Executive Insight. Writes about leadership, decision-making and the parts of building a business that nobody puts in the plan.
Explore other articles
-
Decision-Making
Most executives believe their decisions are limited by the quality of their analysis. Better data, a sharper model, one more week of work. The largest study of real business decisions found the opposite, and the size of the gap is the reason structured decision making is worth taking seriously rather than treating as bureaucracy. Process […]
9 min read -
Decision-Making
It is nine in the evening, the same question is in front of you for the third time today, and you can feel yourself reaching for whichever answer ends the conversation fastest. You already know the phrase for this. Everyone does. The phrase is decision fatigue, and the popular version of it is oversold. The […]
13 min read -
Decision-Making
Most advice on dealing with difficult clients is really advice on being more patient. Stay calm, listen actively, do not take it personally. All true, all useless at 11pm when the fourth revision request arrives with the word “obviously” in it. Patience is a resource you spend. Structure is a resource you build once. Almost […]
7 min read