Decisions under pressure, without pretending to be certain

Pressure does not give a leader permission to create chaos. Nor does it provide extra data or a guarantee that a decision will be right. A good decision under pressure is not about projecting absolute certainty. It is about stating what we know, identifying the risks and taking action that we can deliberately adjust.

Pressure narrows our field of view

As time pressure grows, we naturally want to resolve the situation quickly. We may be tempted to choose the first reasonable option, take full responsibility and act. The opposite extreme is to delay the decision, gather more data and hope uncertainty will disappear on its own. In practice, both reactions can be costly.

My experience in military command and business has taught me that pressure rarely disappears after one forceful announcement. It eases when the team understands the situation, knows the priority and knows what to do next. A leader's role is not to look as though they have every answer. It is to provide enough structure for people to act.

First, establish what actually needs a decision

Under pressure, a problem quickly attracts other issues. A delay becomes tangled up with emotions, accountability, stakeholder communication and blame. Trying to solve everything at once turns a meeting into an exchange of opinions. I start with a simple question: what exactly must we decide now to move the situation forward?

During one distribution centre launch, construction was three months behind schedule, with a real risk of further delay. Analysing every cause would not have opened the facility. We needed to separate critical issues from those that could wait, coordinate the parties involved and focus on the actions with the greatest impact. The pressure remained, but became manageable because decisions had a clear sequence.

Separate facts, assumptions and concerns

In a difficult situation, these three categories often sound alike. A fact is information we can verify. An assumption is a working interpretation that allows us to move despite incomplete data. A concern describes a possible negative outcome. All three matter, but each calls for a different response.

Unless we separate them, the most forcefully expressed concern starts to sound like a certainty. The team may overestimate one risk and miss another. I write the key information in three columns and ask: what do we know, what are we assuming, and what are we simply worried about? Clarifying the language usually improves the conversation.

Choose an option and agree when to change it

A decision under pressure does not have to be irreversible. A staged approach is often better: choose an option, limit exposure to risk and agree immediately when to review it. This is not inconsistency. It is commitment to the goal rather than to our first idea.

Alongside the decision, I record the condition for changing it. That might be a deadline, new information, crossing an agreed threshold or not seeing the expected result. An adjustment then looks less like a leader's failure and more like an agreed part of managing the situation. The team also knows what to monitor and when to report that assumptions no longer hold.

Communication is part of the decision

Even a sound decision fails if everyone understands it differently. After the meeting, people should know not only what we are doing, but why, who owns the next step, when it is due and when we will reassess the situation.

I avoid messages whose only purpose is to reassure. If a risk is real, I name it. But I do not pass the entire burden of uncertainty to the team. I explain the priority, responsibilities and the point at which escalation is needed. That offers more reassurance than simply saying everything will be fine.

After acting, revisit the assumptions

Pressure encourages judging people by outcomes, but makes learning from the process harder. After a decision, it helps to return to three questions: which assumptions were right, what did we miss, and what would help us respond earlier next time? The aim is not to find someone to blame. It is to improve the decision-making system.

In an operationally mature organisation, reflection after action is brief and specific. It may lead to a change in a standard, reporting, an alert threshold or ownership. If the discussion ends with ‘we got through it this time’, we lose the most valuable part of the experience.

Five practical takeaways

Name the one decision that really must be made now. Set the other issues aside.

Separate facts from assumptions and concerns. Do not let forceful opinions replace evidence.

Compare at least two realistic options, considering both the cost of action and the cost of delay.

Agree in advance when to adjust the decision and when to reassess the situation.

Communicate the owner, deadline, next step and escalation threshold.

Tool: the ten-minute decision card

Before a short decision meeting, complete six fields. This is not paperwork for its own sake. One page should contain the chaos, reveal assumptions and lead to a clear next step.

If you still cannot decide after ten minutes, name the missing information, assign someone to obtain it and set a firm deadline to revisit the issue. That, too, is a decision.

Certainty is not a prerequisite for responsibility

A leader does not always have the luxury of complete data. But they can influence whether uncertainty is structured or spreads across the team. To me, responsibility in a difficult situation means naming the risk, taking a deliberate step and being ready to adjust when the facts change.

If your team's decisions get stuck between haste and over-analysis, at Mentavia we can examine decision conversations, accountability and escalation. We work with specific situations rather than ready-made answers detached from your organisation's reality.