See It Through.
Keep the Picture.

Most workload management behaviours are about reducing demand — managing tasks efficiently, delegating, creating spare capacity, keeping the cognitive load below the level where performance degrades. Perseveres in working through problems without reducing safety is the one that asks for the opposite. When the problem is safety-critical and the solution is complex, the crew has to sustain the cognitive investment the problem requires, for as long as it takes, without taking the shortcut of declaring it resolved before it actually is.

That is a different kind of discipline from the efficiency behaviours. It is the discipline of tenacity — of staying with a difficult problem when the path to resolution is not clear, when the easy response would be to accept a partial solution and move on, when the workload of continuing is real and the workload of stopping is immediate relief. The crew that perseveres correctly has weighed that equation and arrived at the right answer: the safety stakes justify the investment.

Two Edges of the Same Behaviour

This behaviour has two distinct expressions, and both matter.

The first is knowing when to persevere. A safety-critical problem that is complex or resistant to easy resolution demands that the crew invest what it takes to solve it fully and correctly. A non-normal that has been partially managed is not a managed non-normal. It is a partially managed situation with an unresolved element that will continue to affect the operation, and may develop further, until it is properly addressed. The crew that accepts an incomplete solution because continuing is difficult has made a workload management choice at safety's expense. That trade is not available.

The second is knowing when not to. Not every problem on a flight demands immediate, full cognitive investment. Some can be correctly assessed as lower priority — present, acknowledged, but not currently affecting the safety of the operation — and deliberately set aside while the crew maintains capacity for what matters more. The decision to shelve a problem is not avoidance. It is correct prioritisation. A crew that pursues every problem with equal tenacity, regardless of urgency, will consume the capacity that the genuinely critical ones require.

The behaviour sits at the intersection of both — the judgment to know which situation demands perseverance, and the professional resolve to deliver it when it does.

The Workload Cost of Solving

Problem-solving consumes cognitive resource. A complex non-normal — one that requires diagnosis, option generation, checklist management, crew coordination, and continuous monitoring of the developing situation — will draw on the same capacity pool that monitoring, SA maintenance and workload management all depend on. Sustained engagement with a difficult problem necessarily reduces the resource available for everything else.

This is the constraint the behaviour must operate within. The crew can persevere through a difficult problem — and should, when safety requires it — but the cost to the wider operation has to be managed. If the problem-solving is consuming SA, the monitoring that keeps the aircraft safe must be preserved through other means. Delegation of non-essential tasks. Explicit crew assignments that ensure the flight continues to be managed even as the problem is being worked. The hold or extended routing that buys time without pressure. The communication to ATC that creates space.

The crew that perseveres correctly is not simply staying with the problem. They are simultaneously managing the workload consequences of staying with it — ensuring that the investment the problem requires does not create a second problem in the wider operation.

SA Cannot Be the Price of the Solution

The qualifier in this behaviour is the most important part of it: without reducing safety. Perseverance that maintains the flight at an unsafe level — that allows the aircraft to be inadequately monitored, that sacrifices the shared mental model, that consumes the capacity needed to recognise and respond to developing threats — is not this behaviour. It is a version of task fixation that has been given a more flattering name.

The problem demands attention. The aircraft demands attention. Both are true simultaneously, and the crew has to manage both simultaneously. The monitoring that keeps the operation safe cannot be suspended because the problem is difficult. The cross-checks, the callouts, the awareness of flight path and fuel and traffic — all of that continues, even as the problem is being worked. The crew member who can sustain the problem-solving without losing the wider picture is the one demonstrating the full behaviour. Not just tenacity. Tenacity without tunnel vision.

This is where the full suite of crew resource management behaviours is required at once. The PM maintaining the picture while the PF works the problem. The explicit task allocation that ensures monitoring continues. The communication that keeps both crew members aware of the developing situation. The workload management that has created enough spare capacity for both demands to be met. All of it has to work together for this behaviour to work at all.

Resolve Is Built in Normal Operations

The tenacity that this behaviour requires under pressure is not summoned on demand. It is an expression of the professional standards and habits built across the entire operation — the same argument that applies to every behaviour in the framework, but with a particular force here.

The crew member who has always completed procedures fully rather than accepting approximate completion, who has always followed through on the verification step rather than assuming the outcome, who has always worked problems to resolution rather than parking them when they became difficult — that crew member has built the professional habit of seeing things through. Under pressure, that habit runs. The problem is worked to its conclusion because that is simply the standard that has always applied.

The crew member whose standard in normal operations is approximate — who sometimes takes shortcuts, who sometimes accepts a partial outcome because completing it fully would require more effort — has no reliable professional resolve to draw on when the difficult problem arrives. The habit that should run under pressure is not there, because it was never consistently built.