Competence Hides Until Tested

Category: Individual behaviour Capability remains invisible until pressure forces it into view.

Before Flight 1549, Chesley “Sully” Sullenberger was an experienced but largely unremarkable commercial pilot. He had no reputation for drama or brilliance. He was known as reliable, methodical, and professional. Nothing about his routine performance distinguished him from the thousands of others doing the same job competently every day.

Shortly after take-off from LaGuardia in January 2009, the aircraft struck a flock of birds and lost both engines. At low altitude over a dense city, there was no checklist that cleanly matched the situation and no time to follow one fully. The options were few, the information incomplete, the margin almost nonexistent.

Under those conditions Sullenberger made a series of rapid judgements. He assessed that returning to the airport was not viable, coordinated calmly with air traffic control, and put the aircraft down on the Hudson River. Everyone survived.

The investigation afterwards showed something telling. Many simulator-trained pilots, following standard procedures, could not achieve the same outcome when placed in the same scenario. The difference was not knowledge of the rules. It was judgement under pressure. Until that moment, Sullenberger’s competence had not been visible. It had simply never been required.

The trouble is that aviation gives us a clean, dramatic version of a thing that usually arrives without drama. So picture the ordinary version. A department runs smoothly for three years under a manager everyone rates highly. She is calm, organised, well-liked; the numbers are good; she is the obvious candidate for the bigger role, and she gets it. What nobody can see is that the department ran well partly because of her and partly because of a stable market, a strong second-in-command, and processes laid down by her predecessor that were quietly doing a great deal of the work. None of that gets tested until the year it all moves at once — a market shift, the deputy leaves, a major customer threatens to walk. Now the role asks for the thing the calm years never asked for: judgement with no template, under real pressure, with people watching. And only now does anyone — including her — find out whether the competence was hers or the structure’s. The promotion was awarded on three years of evidence that, it turns out, tested almost nothing that the new job would demand. That is the same gap as the Hudson, minus the river. It is far more common, and far harder to spot, precisely because nothing crashes.

The Principle

Real competence — judgement under pressure — stays invisible while conditions are stable, because stable conditions never call on it. It only becomes observable at the exact moment it is needed and too late to acquire.

When a system behaves predictably and work follows familiar patterns, the differences between people in judgement, adaptability, and nerve are simply not exercised, and so cannot be seen. Everyone looks capable, because the environment is doing much of the work of keeping them capable. Strip the support away — through a crisis, an exception, a moment with no checklist to follow — and the gap between those who can actually decide and those who were merely riding the structure opens up instantly.

Why It Is Inevitable

Most organisations are deliberately built to reduce variability. Processes, checklists, escalation paths, and defined roles exist precisely so that outcomes do not depend on any individual being exceptional on the day. This is exactly what you want most of the time, and it works — but it has a hidden cost. If the structure is carrying the outcome, then individual judgement is rarely the thing being tested, and so is rarely the thing being seen.

As long as conditions stay inside their expected bounds, people can perform perfectly well on habit, guidance, and the scaffolding around them, and an observer cannot tell who is genuinely capable from who is competently following the rails. So competence gets inferred from whatever proxies are visible instead — confidence, fluency, years served, seniority — none of which is the same thing, and all of which can be present in someone who has never once had to make a hard call alone. Pressure is the only condition that removes the scaffolding and forces the real signal into view, and pressure, by its nature, arrives unannounced.

How It Shows Up

• People who perform well in routine conditions struggling the moment plans break
• Others becoming unexpectedly decisive when discretion is suddenly required
• A spike in escalation precisely when independent judgement is needed — the structure asking for someone to decide, and no one stepping into it
• Rigid adherence to process even as outcomes visibly deteriorate, because the process is the only thing the person actually has
• A capable deputy or a strong predecessor’s leftover system quietly carrying a leader who is credited for the result
• A high performer’s record turning out, on inspection, to coincide exactly with the calmest years their function ever had
• Surprise, both ways, at who copes and who folds when pressure finally arrives

Why It Causes Damage

When competence is assumed rather than tested, organisations place trust in the wrong spots. Responsibility accumulates around the people who look capable in calm conditions — the confident, the fluent, the long-served — and accumulates fastest exactly where it has been verified least. Then pressure arrives, as it always eventually does, and the gaps are exposed at the worst possible moment: when the cost of failure is highest and the room to recover is smallest. The Hudson does not give you a second approach.

It distorts development as much as it distorts trust. People who have never been tested do not know their own limits, and cannot grow against an edge they have never met. People who could handle far more remain invisible, passed over, because the system never created an occasion that would have shown it. So the organisation simultaneously over-trusts the untested and under-uses the capable, and discovers both errors at once, in a crisis, when neither can be fixed in time.

How To Counter It

• Create deliberate, low-risk ways to test judgement before it is critical, rather than waiting for reality to run the test for you at full stakes
• Use simulations, scenarios, stretch assignments, or constrained problem-solving — anything that removes the scaffolding on purpose, in a setting where failing is survivable
• Observe behaviour specifically when information is incomplete and time is short, because that is the only condition that exercises the real signal
• Reward sound decisions made under uncertainty, not just flawless execution of the routine — otherwise you are still measuring scaffolding
• Separate readiness for responsibility from success in stable environments; a calm-conditions track record is evidence of reliability, not of judgement, and the two are not the same

What Good Looks Like

An organisation that holds the distinction clearly: reliability in calm conditions and competence under strain are different things, and a record of the first is not evidence of the second. So it does not wait for a crisis to learn who can decide. It tests people early, safely, and on purpose — stretch assignments, deliberate exposure to ambiguity, rotation through the genuinely hard problems while the stakes are still containable. It promotes on demonstrated judgement, not on proxies. It knows which of its current results are owed to the person and which to the structure around them, and it does not confuse the two. As a result, surprises about who can cope are rare, because the question was answered before the day it mattered — and the people who could handle more were found before they had to prove it the hard way.

A Reflective Question

Whose capability in your organisation has only ever been inferred from calm conditions — and how much of their visible success belongs to them rather than to the structure they have been standing on?