A control room team has ten minutes to respond to a developing fault. The procedure is clear on the technical steps, but conflicting priorities emerge around production, escalation and the potential effect on an adjacent system. The quality of the outcome will not rest on knowledge alone. It will rest on how people read the situation, challenge assumptions, share concerns and make a decision with incomplete information. That is the practical question behind how to improve operational judgement.
In high-risk, highly regulated environments, judgement is often discussed after a serious event. That is too late. Operational judgement shapes ordinary work every day: whether a supervisor stops a job, whether a project lead surfaces a weak signal, whether a contractor questions an unsafe assumption, and whether senior leaders understand the operational consequences of a commercial decision.
It is not a personality trait possessed by a few experienced people. It is a behavioural capability that can be developed, observed and strengthened in the conditions where it matters.
Operational judgement is more than decision-making
Decision-making is the act of choosing. Operational judgement is the disciplined process that makes a choice credible. It combines technical knowledge, situational awareness, risk understanding, operational experience and the willingness to test one’s own view.
That distinction matters because poor judgement rarely begins with a lack of intelligence or effort. More often, it emerges when capable people work with partial information, compressed time, unclear authority or a culture that rewards certainty over challenge. A decision may look reasonable in isolation while still being poorly judged because the team did not examine its assumptions, seek relevant dissent or consider downstream effects.
In complex engineering, defence, nuclear and major contracting environments, the decision itself is only part of the picture. Leaders must also ask: who had the information? Who had the authority to intervene? What concerns were raised? What trade-offs were made explicit? And what behaviour made it easier, or harder, to act on the risk?
Start with the operating conditions, not individual capability
Organisations sometimes respond to judgement failures with a generic course on critical thinking. This can have value, but it will not correct an operating system that consistently creates bad conditions for sound decisions.
Begin by examining where judgement is routinely placed under strain. Look at handovers, shift changes, design reviews, permit decisions, programme recovery meetings, incident escalation and contractor interfaces. These are the points where information is transferred, priorities collide and authority can become blurred.
Three conditions deserve particular attention. First, decision rights must be clear. People need to know what they own, what requires escalation and who can stop work without political cost. Second, information must reach the right people early enough to influence the outcome. Third, teams need behavioural permission to challenge, clarify and slow a decision when uncertainty is material.
This does not mean creating delay for its own sake. In an operational setting, over-escalation can be as damaging as under-escalation. The aim is proportionate judgement: enough scrutiny for the level of risk, without making routine delivery dependent on unnecessary senior approval.
Make trade-offs visible
Most significant operational decisions involve competing demands. Delivery dates, cost, production, safety, quality, workforce capacity and stakeholder commitments can all pull in different directions. Weak judgement hides those tensions behind vague language such as “getting it done” or “being pragmatic”.
Strong judgement names the trade-off. A leader might say: “We can recover two days against the programme, but only by reducing contingency in a system we do not yet fully understand. Is that exposure acceptable, and who is accountable for it?” This changes the conversation. The issue is no longer whether the team is committed. It is whether the decision is based on an explicit and defensible assessment of risk.
Leaders set the standard here. If senior teams privately reward schedule recovery while publicly emphasising safety and assurance, people will quickly learn which priority carries real weight.
Build the behaviours that hold under pressure
The behaviours behind operational judgement are simple to describe and difficult to sustain when pressure rises. They need practice in live operational contexts, not just agreement in a workshop.
The first is disciplined inquiry. Teams should be able to distinguish between what they know, what they assume and what they still need to verify. This requires leaders to ask precise questions rather than invite broad reassurance. “What would change your view?” is often more useful than “Are we confident?”
The second is constructive challenge. A challenge is not a personal objection or a performance of caution. It is a specific test of the decision: the evidence it relies on, the risk it may be missing or the condition that would require a different response. Teams need a common language for raising this challenge without creating defensiveness.
The third is calibrated confidence. Operational leaders must make decisions before every uncertainty is resolved. Waiting for perfect information can create its own risk. Calibrated confidence means being clear about the confidence level, the safeguards in place and the trigger points for reassessment.
Finally, teams need closure. Decisions should record the rationale, assumptions, owner and review point. This is not bureaucracy. It prevents a temporary judgement call from becoming an unexamined operating norm after the conditions have changed.
Use simulations to expose judgement, not just test knowledge
Operational judgement improves when people can rehearse difficult decisions without paying the price of getting them wrong in live work. Well-designed simulations are valuable because they reveal behavioural patterns that normal meetings conceal.
A realistic scenario can introduce competing data, an ambiguous procedure, a stakeholder demand and a time constraint. Observers can then examine how the team established facts, shared authority, handled challenge and committed to a course of action. The learning is not limited to whether the final answer was technically correct. It lies in the quality of the process that produced it.
The scenario must be credible. Generic case studies will not expose the habits that affect a nuclear outage, a complex construction programme or a safety-critical maintenance decision. The pressure, language, interfaces and consequences must reflect the work people actually do.
This is also where senior leaders should participate, not merely sponsor the activity. Their own response to uncertainty sends a powerful signal about whether challenge is genuinely welcome and whether evidence can override hierarchy.
Measure behavioural drift before it becomes an event
Judgement is not strengthened by training alone. Organisations need evidence of whether the intended behaviours are showing up in day-to-day work.
Traditional engagement surveys and retrospective incident reviews provide part of the picture, but they are often too broad or too late. More useful measures focus on the live behavioural conditions that shape decisions: whether people can raise concerns, whether cross-functional teams resolve issues quickly, whether leaders seek disconfirming evidence, whether decision rights are understood, and whether known risks are being normalised.
This requires more than a single score. Patterns matter. A deterioration in challenge at one project interface, for example, may be more operationally significant than a stable organisation-wide average. Equally, a team may report high trust while still avoiding difficult conversations about programme pressure. The evidence needs interpretation alongside operational context.
TEG’s approach combines practical development with behavioural insight for this reason. The objective is not to declare that a leadership intervention has been completed. It is to establish whether leadership behaviour is changing the quality, speed and reliability of operational decisions.
Review decisions without turning review into blame
A good decision can produce a poor outcome because conditions change. A poor decision can occasionally produce a good outcome through luck. Reviewing judgement solely through results encourages hindsight bias and defensive reporting.
Instead, review the decision at the point it was made. What information was available? Which assumptions appeared reasonable? What alternative actions were considered? Was dissent heard? Were escalation thresholds clear? This approach identifies learning without excusing weak practice.
Short, routine decision reviews are usually more effective than waiting for a major incident. They create a habit of operational reflection and help teams recognise recurring patterns: optimism around recovery plans, reluctance to stop work, missing stakeholder voices or excessive dependence on a single expert.
Give leaders a visible role in raising the standard
Senior leaders cannot delegate operational judgement to the frontline and then judge it only through lagging indicators. Their behaviour defines the environment in which others make decisions.
That means being present at the points where work is planned and risk is discussed. It means asking for evidence, not certainty; making trade-offs explicit; protecting those who raise legitimate concerns; and refusing to reward heroic recovery at the expense of disciplined control. It also means admitting when a previous decision needs to be revised. Leaders who treat revision as failure teach teams to defend weak positions for too long.
The practical test is straightforward: when pressure rises, do people become clearer about risk, ownership and next actions, or do they become quieter, faster and less willing to challenge? The answer will reveal far more about operational judgement than any leadership statement.