Fast Decisions vs Deep Decisions: Which to Choose in Each Situation

A sales director who decides in five minutes which proposal to send a client is doing their job well. The same director deciding in five minutes on a restructuring that affects a hundred jobs is almost certainly making a mistake that will only surface months later. The difference is not in the person's ability. It is in the type of decision the situation calls for.

Many executive teams have never openly discussed this distinction. They treat every decision the same way, either everything goes through a long meeting and a committee, or everything gets settled quickly in a chat exchange, regardless of what is actually at stake. This lack of calibration costs dearly both ways, delaying what should be fast and rushing what needed more time.

When does it pay to decide fast?

It pays to decide fast when the cost of getting it wrong is low and correcting it is easy. Testing a new message in a campaign, adjusting a price on one channel, choosing between two similar suppliers for a routine purchase, these are decisions where speed carries more value than exhaustive analysis, because the mistake, if it happens, costs little and teaches fast.

In these situations, over-hesitating carries its own cost. A team that treats a reversible, low-risk decision with the same exaggerated care it would reserve for a strategic one is wasting time and energy that would be needed elsewhere.

What type of decision demands depth?

Decisions with consequences hard to reverse demand depth: a merger, a partner's departure, a change of business model, a decision on whether to dismiss or keep someone in a senior position. In these cases, the cost of deciding fast and getting it wrong is not limited to lost time. It extends to relationships, reputation and trust that take years to rebuild once damaged, often longer than it took to build the business itself to the point it was at before the mistake.

These decisions benefit from time, not because the information is slow to arrive, but because the internal structure needed to process it well, the discussion, the honest disagreement, the consideration of who will be affected, demands more than a quick impulse can offer.

Why do experienced executives decide badly under pressure?

The Last Asset describes cases of highly experienced managers who, under pressure, make decisions that any later analysis identifies as wrong. The cause is rarely a lack of information. It is a lack of internal structure, the inability to tolerate uncertainty long enough to let the right decision emerge, instead of grabbing the first option that eases the discomfort of not knowing.

An executive under pressure feels an urgency to decide even when the situation does not actually call for it. That felt urgency is often confused with the situation's real urgency, and telling the two apart is precisely what technical experience, without self-knowledge work, does not teach.

What does the phrase "speed without consciousness is self-consuming" mean?

Hélder Teixeira uses this phrase to describe what happens when an organisation speeds up decisions without having done the consciousness work that would sustain that speed. Self-consuming means the system feeds on itself, scaling the mistake with the same efficiency it would scale the win, because speed on its own does not tell the two apart.

A team that decides fast and well has, behind that speed, a great deal of invisible structure: trust between members, clarity about who decides what, and enough prior discussion that the fast decision is not improvised, but the application of a judgement already prepared. Without that structure, deciding fast is just deciding badly, faster.

How do you know a fast decision will cost you later?

One warning sign is feeling the need to decide alone, without involving whoever would normally take part, just to avoid the delay of a conversation. Another is the absence of any question about reversibility before moving forward: if this decision goes wrong, how much does it cost and how long does it take to fix?

A third sign is when the rush to decide comes from emotional discomfort with uncertainty, rather than a real demand from the business calendar. A decision maturity diagnostic, such as Evomatrix, helps tell these two types of pressure apart in a team, showing whether the habitual speed comes from structural clarity or from poorly managed aversion to uncertainty.

It is also worth asking who in the room is usually the voice that pumps the brakes and asks for more time, and how that person gets treated when they do it. If that voice is systematically ignored or seen as an obstacle to progress, the team has built a silent incentive to rush even situations that deserved more care, and it will keep doing so until a costly mistake forces the habit to be reviewed.

What should you do after a fast decision that went wrong?

The most useful step is not hunting for who failed. It is asking, honestly, whether the situation was misclassified from the start, treated as reversible when it was not, or whether the team had the right information but lacked the structure to discuss it in time. This distinction stops the mistake being repeated for a different reason next time.

Companies that do this exercise regularly develop, over time, a sharper instinct for what type of decision they are facing before they even resolve it, which on its own already cuts the number of badly chosen fast decisions that get made.