Treat Setbacks as Data, Not Diagnosis: A Leadership Lesson From the Cockpit

When a commercial aircraft has a bad day, the industry does not gather to decide who to blame. It pulls the flight data recorder, reconstructs the sequence of events, and asks a single practical question: what would make the next flight safer? That instinct, so ordinary inside aviation, turns out to be surprisingly rare everywhere else. Most of us, when a plan collapses, reach first for a verdict about ourselves rather than a record of what actually happened.

That gap between judging a failure and studying it is where a lot of leadership is won or lost. And it is the idea at the center of the work of Cleous “GloWry” Young, a former behavioral therapist in Philadelphia who rebuilt his own thinking after a hard year by borrowing the diagnostic discipline of the cockpit. His framework is one illustration. The underlying principle is available to anyone who leads a team, a family, or just themselves.

The difference between a diagnosis and a data point

A diagnosis is a label. It tells you what something is and, usually, closes the file. A data point is different. It is a neutral observation that only becomes useful when you place it alongside other observations and look for a pattern. The two feel similar in the moment of a setback, but they lead in opposite directions. A label invites shame, defensiveness, or resignation. A data point invites investigation.

Young’s own turning point came after he left a stable job in 2018, entered a business partnership that failed quickly, and fell into what he later described as his worst year. His instinct at first was the common one: to ask what was wrong with him. The shift happened when he stopped treating the experience as a verdict and started treating it as a recording. Rather than asking why the partnership failed, he reviewed the conditions, decisions, relationships, and pressures that surrounded it, including patterns that predated the business entirely. The failure, in that light, was not the cause of his distress. It was one more entry in a longer log.

You do not have to adopt his specific vocabulary to use the move. The transferable skill is separating the event from the evidence. A missed quarter, a lost client, a blown launch, a fractured relationship: each can be held as a sentence passed on your character, or as information about a system that produced a result. Only the second version gives you something to work with.

Why the black-box mindset builds resilience

Resilience is often described as toughness, the capacity to absorb a blow and keep going. But raw endurance without learning just means taking the same hit repeatedly. The more durable form of resilience is the ability to metabolize an experience quickly enough that it informs the next decision instead of haunting it.

Aviation is a useful model here precisely because the industry improved its safety record not by asking people to try harder inside the existing system, but by redesigning how it captured and reviewed information. The recorder is blameless by design. Its job is to make the next flight better, not to indict the last crew. When leaders internalize that posture, two things happen. The fear of failure drops, because failure stops being a personal indictment. And the speed of learning rises, because energy that would have gone into defending or explaining goes into understanding instead.

There is an old observation, usually attributed to Einstein, that a problem cannot be solved with the same thinking that created it. Whatever its exact origin, it names the trap well. Communities, companies, and individuals often meet a recurring problem by applying more of the effort that was already failing. The black-box mindset breaks that loop by forcing a change in the level of analysis, from “who is at fault” to “what conditions produced this.”

Reading the instrument panel: signals worth trusting

Part of Young’s approach rests on a simple observation about the body: that gut-level unease often arrives before the conscious mind can articulate why. Most experienced leaders know the feeling. Something about a hire, a deal, or a direction registers as wrong before the reasons are clear. The mistake is treating that signal as noise to be overridden rather than an instrument reading to be investigated.

This does not mean every anxious flutter is prophecy. Instruments can be miscalibrated, and fear can masquerade as intuition. The disciplined response is neither to obey the feeling blindly nor to dismiss it, but to log it and check it against the facts. In practice that looks like naming the discomfort, asking what specifically triggered it, and looking for corroborating data before deciding whether it is a warning or just static. What communities and workplaces often label as overreaction can, on inspection, turn out to be an accurate reading that no one bothered to investigate.

Applying disciplined thinking under pressure

The hardest place to think clearly is inside the pressure itself. When a setback is fresh, the nervous system is loud and the temptation is to react. Aviation handles this with procedure: a defined set of questions that a crew or an investigation board works through regardless of how they feel. Borrowing that structure, a leader facing a bad outcome can run a short, repeatable review:

• What conditions were present before the event? Workload, incentives, fatigue, unspoken assumptions, external pressure.
• Where did communication break down? What was known but not said, or said but not heard.
• What older patterns showed up here? The histories and habits people bring into a situation that shape how they read it.
• What would “returning to the gate” require? The honest step back needed before moving forward, rather than pressing on out of momentum.
• What would a safe path forward actually demand? The concrete changes, not the intentions.

The value of a checklist like this is that it works when you are not at your best. It replaces the swirl of self-judgment with a sequence of answerable questions, and it produces a record you can act on. Notice that none of the questions ask whose fault it was. That omission is deliberate, and it is what allows the review to happen honestly, because no one has to defend themselves to participate.

The load you carry versus the load you clear

Young offers a homely image for what unexamined experience does to us: an overstuffed suitcase, where every item presses against every other because nothing has been unpacked. It is a useful picture of how unresolved pressure accumulates. Old disappointments that were never reviewed do not disappear; they sit in the bag and add weight to whatever comes next. A fresh setback feels unbearable partly because it lands on top of everything already packed.

The leadership application is straightforward. Reviewing experiences as they happen, rather than stuffing them away, keeps the load light enough to carry. Teams that hold honest, blameless retrospectives after both wins and losses travel lighter than teams that only ever move forward. So do individuals. The unpacking is not indulgence; it is maintenance. An aircraft that never gets its data reviewed is not braver than one that does. It is just less informed about its own condition.

The bottom line

You will not control most of the events that test your leadership. You can control whether you treat them as verdicts or as evidence. The practical discipline is small and repeatable: when something goes wrong, resist the rush to label yourself or someone else, and instead reconstruct the conditions that produced the outcome. Trust the early warning signals your instincts send, but verify them against facts before acting. Run a consistent review after failures and successes alike, and keep the questions aimed at conditions rather than blame. Unpack the load as you go, so old pressure does not compound the new.

None of this requires an aviation background. It requires a decision about what a setback means. Held as a diagnosis, it closes doors. Held as data, it becomes the most honest information you will ever get about how to fly the next leg better.