You've had this conversation on the packing mat. Guaranteed.
Someone walks in from the landing area, buzzing, storytelling. The spot was long, the winds had picked way up, and they ended up landing out, but somehow it all worked out. They're grinning; laughing. The jump is being filed under "good."
Was it?
Annie Duke—former professional poker player, decision scientist, author of Thinking in Bets—has a useful word for what's happening here. She calls it “resulting”: the cognitive habit of judging the quality of a decision by the quality of its outcome. Win the hand, good call. Lose the hand, bad call. Landed safely? Getting out over a deck of cloud was a good decision! Landed in a tree? Getting out over a deck of cloud was a bad decision!
It feels intuitive. It's also wrong.
They ain’t the same thing
A decision is what you do with the information you have, under the pressure you're under, at the moment you have to choose. An outcome is what happens next.
Skydiving sits in the gap between those two things more uncomfortably than almost any other activity, because the gap contains gravity, weather, gear, other jumpers, and a not-insignificant amount of luck.
Duke's framework asks you to assess the decision on its own terms. Given what you knew at the time, given the probabilities you could reasonably estimate, given your skill level and your currency and the conditions—was the choice you made a good one? The answer to that question is independent of how the jump went.
This matters because skydiving gives us extremely noisy feedback. A jumper can make a marginal weather call, get bumped around on final, scratch out a survivable PLF, and walk away having learned the exact wrong lesson: that what they chose to do was “fine”. Conversely, a jumper can make a textbook-correct call to sit a load out and watch everyone else have a perfectly nice skydive.
The decision was right. The outcome made it look conservative.
"Resulting" is not your friend
The danger is cumulative. Every time we let a good outcome validate a poor decision, we lower our threshold a notch. The marginal weather call that worked becomes the baseline for the next marginal weather call—except now the conditions are slightly worse, because last time was "fine." The mis-timed high-performance landing that didn't bite back becomes the default. The decision to cut away that we delayed past decision altitude (but got away with because there happened to be enough margin of error) becomes a story we tell—instead of a near miss we soberly examine.
Walk around any DZ and you can hear this happening in real time. The jumper who says "I've done it loads of times and never had a problem" is not making an argument about the quality of their decision-making. They're making an argument about their outcomes. Those are different claims, and conflating them is how experienced jumpers end up in incident reports.
How to stop resulting
Duke's prescription is straightforward and harder than it sounds. After a jump, separate the two questions deliberately.
Question one: Was the outcome what I wanted? Easy. You either landed where you meant to, flew the jump you dirt-dove, made the formation, hit the gate. Or you didn't.
Question two: Regardless of the outcome, was the decision a good one? This is where the work is. It requires honesty about what you knew at the time—not what you know now, with the benefit of having seen how it played out. It requires you to imagine the same decision playing out a hundred times and ask what percentage of those would have gone well. A decision that works seven times out of ten is a good decision that sometimes produces bad outcomes. A decision that works ninety-nine times out of a hundred is a good decision that, on the hundredth jump, can still kill you.
The jumpers who survive long careers in this sport tend to be the ones who can debrief a perfectly successful jump and conclude I got away with that one. They've decoupled the two assessments. They're not punishing themselves for the good outcome; they're refusing to let it launder a sloppy decision.
The inverse case
It works the other way too, and this is the part that gets undersold. A jumper who scrubs a load because the spot looks bad, the winds are squirrelly, or something about the manifest feels off—and then watches the load come down uneventfully—has not made a bad decision. They've made a good decision with an outcome that, in isolation, makes them look “cautious”.
If we only celebrate the decisions that produce visible wins, we train each other to chase outcomes. The jumper who sits a load out deserves the same respect as the jumper who flies the dive. Often more, because saying no is harder.
The bet you're actually making
Every jump is a bet.
The information is incomplete, the variables are partly outside your control, and the stakes are not symmetrical—the cost of a bad outcome is wildly disproportionate to the cost of a missed jump. Duke's framework doesn't tell you not to bet. It tells you to be honest about what you're betting on, what the odds actually are, and whether the result of any single bet is telling you anything useful about the quality of your wager.
The next time someone throws their canopy on the packing mat next to you and starts telling you about their miraculously-okay sh*tshow jump, try responding with an off-menu question. Try: “Glad you’re okay! What would you do differently?” If the answer is "nothing"—and the jump involved an obviously marginal call—you're talking to someone who's resulting. Gently, and as a friend, you might point that out.
Annie Duke's Thinking in Bets: Making Smarter Decisions When You Don't Have All the Facts (Portfolio, 2018) is worth every skydiver's time.
