In this piece
After a mistake, I can lose the next move before I make it.
In chess, my eyes return to the blunder instead of reading the position on the board. In programming, I replay the command that caused an incident while the system still needs a safe decision. The event has ended, yet part of my attention remains inside it.
Pierre-Henri “Até” Chuet gives this problem a sharper form in Au-delà du cockpit. A former French naval aviator, he writes about a profession where yesterday’s skill cannot land today’s aircraft. On a carrier, a pass is an attempt to land. Each one puts the pilot, the deck crew, the aircraft, and the ship back into the calculation.
His phrase “You are only as good as your next pass” can sound brutal when removed from that setting. I read it as a claim about operational competence, never human worth. Experience earns better judgment. It does not grant immunity from the next mistake.
The question I want to carry from the cockpit into ordinary practice is simple:
How do I learn from the last attempt without letting it fly the next one?
The Two Ways a Past Result Distorts the Present
A bad result can produce shame, stiffness, and haste. I want to recover what I lost, so I force the next move. A good result carries a different danger. Confidence turns into entitlement, and preparation begins to feel optional.
Both reactions make the last result too important. One says, “I failed, therefore I will fail again.” The other says, “I succeeded, therefore I already know how this will go.” Neither statement looks closely at the current conditions.
Até’s phrase cuts through both. The previous pass has already become experience. The next pass still requires attention.
This distinction matters because performance and dignity belong to different categories. My work can be careless. My judgment can be wrong. I can owe someone an apology or a repair. None of this makes my worth rise and fall with an output. I have written elsewhere about preferring verbs to nouns because a verb leaves room to act again. The next pass applies that idea under pressure: responsibility remains active even when identity feels threatened.
Stay Ahead of the Aircraft
Até describes the need to stay “ahead of the aircraft.” A pilot must control the present action while retaining enough awareness to prepare the next one. Thinking about the landing during takeoff can spoil the takeoff. Waiting until every event arrives before considering what follows leaves the pilot reacting late.
The useful position sits between obsession and surprise: do this step well, and know the next step.
Chess makes the pattern visible. Suppose I hang a pawn. If I spend the next five minutes proving to myself that the blunder was understandable, I am no longer analyzing the position. If I launch an unsound attack to “win it back,” the previous move has chosen the next one. The board asks a narrower question: given the position that exists, what is the strongest move now?
Programming asks the same question during an incident. A deployment breaks a production service. The immediate job is to stabilize the system: stop the rollout, restore a known-good version, check the data, and confirm recovery. The perfect architecture can wait. So can the argument about who approved the change. The current state determines the next safe operation.
Presence here is practical, not mystical. It means giving the current decision the information it deserves. For decisions distorted by inherited rules or postponed happiness, I use a separate three-question check.
Debriefing Ends the Attempt
“The past is past” becomes dangerous when it excuses avoidance. A mission does not become useful merely because it ended. Até treats preparation, action, and debriefing as parts of the same work. The debrief reconstructs what happened, finds the gap between plan and result, and changes what the team will do next.
This is the boundary between analysis and rumination.
Rumination asks why I am the sort of person who made the mistake. Analysis asks what conditions produced it. Rumination repeats the emotional charge. Analysis produces a change in behavior, a checklist, a clearer standard, a repaired tool, or a better briefing.
The distinction does not remove responsibility. It makes responsibility specific. After an error, I can ask:
- What happened, in observable terms?
- What did I expect to happen?
- Where did the two paths separate?
- What will change before the next attempt?
Sometimes the answer is personal: I rushed, ignored a warning, or failed to ask for help. Sometimes the system invited the error through an unclear standard, weak training, missing review, or poor communication. Honest debriefing can hold both. Blame wants a culprit. Responsibility wants fewer repetitions.
When another person was harmed, a process change alone is insufficient. The damage may require acknowledgment, apology, and repair. Starting again has moral conditions as well as operational ones. I will explore that separately in this series rather than compressing forgiveness into a productivity technique.
The useful rule is:
Carry the lesson into the next action. Leave the emotional residue behind.
The first half prevents denial. The second prevents the error from taking command.
A Five-Minute Next-Pass Review
I use a short review when an attempt keeps occupying more attention than it deserves. It fits on one page:
Facts. Write three sentences describing what happened without adjectives about yourself.
Effect. Name what the result changed: time lost, trust damaged, data at risk, position worsened.
Lesson. Record one cause that you can influence. Avoid lessons such as “be more careful.” Name the missing behaviour or condition.
Repair. Write the action needed to restore safety or trust.
Next pass. Define the next observable action and when you will take it.
Then stop the review. More writing is useful only if it changes the decision. This limit keeps debriefing from becoming a private trial.
The exercise also works after success. Which preparation made the result possible? Which part depended on luck? What must be repeated deliberately? A strong pass deserves study without becoming a promise about the next one.
This is how I understand Até’s lesson. The past explains the current position. It gives me evidence, responsibility, and experience. It cannot move the next piece, restore the service, or land the aircraft.
Debrief the last pass. Then give the next one your full attention.
Filed under
Explore this subject