A control room has received partial information. A venue manager is worried about an emerging concern. Operations want to continue, security wants to pause, and senior leaders want an answer quickly. This is where organisations learn whether they know how to improve team decisions, or whether they merely have meetings that produce a reassuring record.
Poor decisions are rarely caused by a lack of intelligence alone. More often, the team has failed to establish what matters, separate fact from assumption, challenge its first conclusion or make clear who owns the final call. Under pressure, people tend to protect routine, hierarchy and personal credibility. None of those are reliable substitutes for judgement.
The aim is not to make every decision slow or unanimous. It is to make decisions proportionate, explainable and capable of being acted upon by the people responsible for delivery.
Start with the decision, not the discussion
Teams often spend too long exchanging information without defining the decision required. This creates activity without direction. A meeting can appear thorough while leaving the operational question untouched.
State the decision in a sentence. For example: should the event proceed with additional controls, be delayed while information is verified, or be stopped? Is the team deciding whether a risk is credible, what immediate action is justified, or who needs to be informed? These are different questions and need different evidence.
This discipline also exposes false urgency. Some matters need an immediate protective action while the fuller assessment continues. Others can wait for better information. Treating every issue as a crisis degrades judgement and exhausts the people expected to respond.
A useful team separates three things: what is known, what is believed, and what must be checked. The distinction sounds basic, but it is frequently lost when reports are incomplete, people are anxious or an influential individual speaks first. Assumptions can be necessary. They should never be allowed to masquerade as facts.
Build a shared picture of risk
A shared picture is not everyone holding the same opinion. It is everyone understanding the situation, the uncertainty and the consequence of being wrong.
In protective security and crisis management, teams should consider consequence alongside likelihood. A low probability concern may still justify action if the potential harm is serious and the available control is reasonable. Equally, a plausible concern does not automatically justify disruptive action if the evidence is weak and the proposed measure adds little protection.
The question is not simply, “Could this happen?” Almost anything could. Ask instead: “What is the credible pathway, what would indicate it is becoming more likely, and what can we do now that reduces exposure?” This turns vague concern into an operational assessment.
Context matters. A response that is sensible at a busy public venue may be excessive in a controlled workplace. A construction site, transport interchange and corporate office do not face identical risks or have identical options. Teams improve when they understand the environment well enough to avoid copying controls from a policy or another organisation without asking whether they will work locally.
Give challenge a defined place
Many teams claim to welcome challenge. In practice, challenge is often interpreted as delay, disloyalty or lack of confidence. That is particularly dangerous where seniority is strong and time is limited. The first confident view can become the team’s view before it has earned that status.
A designated challenger is a practical safeguard. Their role is not to oppose every proposal. It is to test the reasoning: What evidence would change our mind? What have we discounted too quickly? What is the consequence if our assumption is wrong? Are we choosing this option because it is effective, or because it is familiar?
The most useful challenge is specific and connected to the decision. General scepticism adds noise. A clear question can expose a weakness before it becomes an incident, a failed response or an avoidable loss of confidence.
Leaders set the standard here. If a team leader becomes defensive when questioned, people soon learn to stay quiet. If they ask for contrary evidence and visibly consider it, challenge becomes part of the work rather than a personal confrontation. This is a behavioural issue, not a meeting technique.
Match authority to accountability
Teams make weak decisions when accountability is blurred. Everyone contributes, but nobody is clear who can decide. The result is delay, escalation for its own sake or action taken by people who lack the authority to sustain it.
Before pressure builds, establish who holds decision authority at different levels of risk. That authority should be close enough to the problem to understand the operational reality, but connected to senior leadership where consequences extend beyond the immediate site or shift.
The decision maker should hear the relevant views, state the chosen action and explain the rationale in plain language. They do not need universal agreement. They do need to show that material concerns were heard and that the decision is proportionate to the information available.
There is also a distinction between deciding and implementing. A senior manager may decide to alter an operational posture, but supervisors and frontline staff will determine whether that decision works. If they do not understand the intent, controls can become inconsistent, impractical or quietly ignored.
Use simple decision disciplines
Complex models can be valuable in planning, but they rarely help a team facing an immediate and uncertain situation. Under pressure, a short, repeatable discipline is more likely to be used.
A good decision conversation should establish the following:
- What decision is required now?
- What do we know, and what remains uncertain?
- What are the realistic options and consequences?
- Who owns the action, communications and review?
This is not paperwork. It is a way of preventing predictable failures: acting on rumour, debating irrelevant detail, overlooking a practical option or assuming someone else will do the follow-up.
Teams should also record significant decisions briefly, particularly where safety, security, service continuity or public confidence could be affected. The purpose is not to create a defensive file. It is to preserve the rationale, assumptions and actions while they are still clear. In a later review, this makes it possible to learn whether the judgement was sound given the information available, rather than judging people solely by the eventual outcome.
Rehearse judgement, not just procedure
A plan may set out roles and escalation routes, but plans do not create judgement. People need opportunities to make choices with incomplete information, competing priorities and realistic constraints.
Tabletop exercises are useful when they force decisions rather than invite broad discussion. Give teams a scenario, a time limit and a decision point. Introduce new information only where it tests an assumption or forces a reassessment. Then examine why the team chose its course of action, what it missed and how it communicated its intent.
The uncomfortable truth is that some teams discover their weaknesses only during a live incident because training has focused on completion rather than capability. Attendance records and certificates may satisfy an administrative requirement. They do not show whether a team can recognise uncertainty, challenge flawed reasoning or make a defensible call under pressure.
Capability evaluation can identify where this gap sits. Is the problem technical knowledge, situational awareness, leadership behaviour, escalation, communication or confidence? The answer should shape development. Generic training for a specific weakness is an expensive way to preserve the weakness.
Review decisions without turning review into blame
A decision review should be routine after significant events, near misses, exercises and complex operational changes. It should be close enough to the event that details remain reliable, but structured enough to avoid becoming a debate about personalities.
Ask what information was available, how the team interpreted it, what alternatives were considered and what happened when the decision met reality. Look especially for workarounds. They often reveal that a control was not practical, an instruction was unclear or responsibility was misunderstood.
Good reviews distinguish between a poor outcome and a poor decision. A sensible decision can still produce an unfavourable outcome because uncertainty is real. Conversely, a successful outcome can conceal weak reasoning or luck. If teams only reward outcomes, they will learn the wrong lessons.
Better team decisions come from clear intent, honest information, purposeful challenge and leaders who treat judgement as a capability to be developed. When pressure rises, the organisation will not fall back on its policy library. It will fall back on the quality of its people’s thinking and the habits they have practised together.
