The Illusion of Inevitability

The moment we call luck destiny, our next judgment goes wrong. Telling luck from skill is where good decision-making begins.

Say two people meet at exactly the right time, in exactly the right place, fall in love, and end up in a happy marriage. Most people who hear this story reach for the word "fate" rather than "coincidence." They want to believe some force beyond human agency arranged this ending in advance.

The story of a startup founder whose company grew improbably fast follows a similar path. The media and the public go looking for a cause. They comb through the founder's experiences, the character those experiences supposedly shaped, even the memories of people who knew them as a child — gathering evidence of a prodigy in the making, connecting dot to dot. But how much did this one person actually contribute to the company's explosive growth? Is it really as much as we imagine?

The two stories share one thing: we already know the ending before we hear them. The love story has already ended in a happy marriage; the founder's story has already ended in success. Once you know the ending and trace the past backward, only the path that leads there stands out clearly. The countless other lives that would have unfolded if the two hadn't met that day, the countless other companies that might have existed had the founder chosen differently — none of that ever enters the frame. We see the one path that actually happened and mistake it for the only path that could have happened. The uncertainty of that moment is forgotten. Only the certainty of the result remains.

Homo Fictus: The Storytelling Animal

To answer this, we need to look at ourselves first. Humans carry an instinct worth calling Homo Fictus — the storytelling animal. When information leaves a gap, we can't leave it alone. We fill it with a story. Faced with a handful of disconnected events, we automatically assign correlation and causation, patching the empty space with narrative. Only then does the world feel like a place we can understand.

The trouble is that this instinct routinely misreads actual correlation and causation. The world runs, in real time, at a level of complexity that easily outstrips human intelligence. Fully reconstructing the trigger that set an event in motion, the conditions that made that trigger possible, and the entire causal chain that followed — this is close to impossible. And yet we compress that tangled chain into a few points and call the compression "the cause."

Two errors are born here: mistaking two unrelated events for related ones — an error of correlation — and pointing to something that isn't the real cause as the cause — an error of causation. Both are dangerous for the same reason: they don't stop at the illusion of the present moment. We file this false causation away as grounds for the next decision, and when a similar situation comes around, we expect the same result. But the odds of that result actually repeating are far lower than we assume. That something worked once is no evidence that it will work again.

Let's give this misunderstanding a name: **the retroactive editing of luck** — the habit of already knowing the outcome, then reaching back into the past to assemble a cause that fits it. The editing always moves toward the ending. Which is why the edited past always looks cleaner, and far more convincing, than the past that actually happened.

Mistaking luck for destiny sets us up to expect an outcome that will not repeat.

Mistaking luck for destiny sets us up to expect an outcome that will not repeat.

What Do Red Underwear and Winning Have in Common?

There's a case that shows how far this psychological misreading reaches — even into the smallest things. An athlete who insists on wearing red underwear before every important match. Common sense says the color of one's underwear can't possibly affect the outcome of a game. And yet, to that athlete, the color feels like serious business.

The reason is simple. After winning a match they desperately wanted to win, the athlete's mind fills with one question: what influenced this? The more desperately someone wants to find a cause, the more willing they are to turn even the most illogical correlation into a story. The color of the underwear, the order in which the shoes go on — anything that happened to sit close in time to a good result becomes a candidate. And once the story is built, it stops being something to test again and becomes a rule to protect. The instinct to regain a sense of control in the face of uncertainty is understandable. But feeling in control and actually controlling the outcome are two entirely different things.

Organizations behave much like this individual with his superstition. It isn't rare for a meeting format, a reporting template, even the seating chart of a team that happened to perform well one year to be singled out as "what made that success" and transplanted wholesale into another team — with no one ever separately verifying what actually drove the result. The individual's red underwear becomes, at the organizational level, "our own formula for success." Different in form, identical in structure: promoting something that merely happened to be nearby into a cause.

Why Do Success Stories Sound More Convincing Than They Are?

The narrative of a successful person is where this instinct performs its most elaborate act. When a founder recalls, in an interview, what made them succeed, that recollection is usually not a record of fact but a story reconstructed after the fact. Once you already know the outcome and trace backward for a cause, of the countless accidental forks that must have existed, only the one path that led to this result comes into view. The other paths — the countless cases where people made the exact same call but ended in failure — never make it into the story to begin with.

This common distortion already has a name: survivorship bias. We look only at the cases that survived, and call whatever they share the secret to success, with no way of checking whether the cases that failed shared the very same trait. This distortion has, in fact, been pointed out repeatedly in business writing. It's well known that when the case studies collected in once-celebrated books about "great companies" were re-examined years later, a considerable number of those companies had already stumbled or collapsed. That doesn't mean the books were wrong, exactly — it means the traits they identified were probably never the cause of success at all, just common background conditions of that particular era. The companies that failed may well have shared the same traits. They simply never made it into the case study to begin with.

The structure of media interviews plays along with this illusion. A reporter asks a founder, "What was the secret to your success?" and the founder has to give an answer. "Honestly, a lot of it was luck" rarely makes a good story. So the founder, the reporter, and the reader end up quietly collaborating to complete a plausible causation. No one is really lying. It's simply that an answer capable of becoming a story gets chosen over one that can't. The story, once finished, is passed down to the next generation of founders as a "success formula" — and no small number of people who follow it to the letter fail, without ever understanding why the same result didn't come to them.

Outcome Bias: When a Good Result Buries a Bad Decision

There's one more name for this illusion: outcome bias — the tendency to judge a decision not by its quality but by whatever result it happened to produce. If the result is good, the decision gets retroactively promoted to a wise one. If the result is bad, even a decision built on solid reasoning gets retroactively demoted to a reckless one.

This bias shows up constantly in marketing meeting rooms. Say a team pushes ahead with a campaign built on thin reasoning and an overextended budget — and, by sheer coincidence, a competitor gets caught in a major controversy at exactly that moment, and sales spike from the spillover. Next quarter's report records this campaign as a win: "the bold bet paid off." The team burns through its budget the same reckless way on the next one. They've mistaken an ungrounded bet that happened to land for a repeatable strategy. Now flip it: another team carefully reviews the data and minimizes risk, preparing a cautious, well-reasoned campaign — only to fall short of expectations because of an unforeseen external variable, say, a temporary slowdown across an entirely unrelated industry. That campaign gets tagged "failed because it played it too safe," and the team's careful way of deciding loses credibility in the next meeting. Had both teams been judged on the quality of their process rather than the size of their result, they would have drawn exactly the opposite lessons.

A good outcome is not proof of a good decision. It is only an outcome.

A good outcome is not proof of a good decision. It is only an outcome.

What makes outcome bias dangerous is that it inverts the direction an organization learns in. Someone with good judgment gets reprimanded after bad luck. Someone with bad judgment gets promoted after good luck. Repeat that pattern even a few times, and the whole organization starts learning "lucky recklessness."

This illusion grows especially strong during a winning streak. String together two or three good results by chance, and a person starts to feel they're "on a roll" — and everyone around them reads that streak as a rise in skill. But three heads in a row out of ten coin flips isn't, by itself, a rare event. Even a random process naturally contains accidental streaks. The problem is that the person witnessing the streak can't accept randomness for what it is — they insist on attaching a cause to it. The storytelling instinct fires identically in the moment of success and in the moment of failure.

How Do You Actually Separate Luck From Skill?

So what can we do about this narrative instinct? The starting point is to consciously split the domain of luck from the domain of skill.

The domain of skill is where similar results recur when the same conditions are repeated. The ability to read data accurately, to define a customer's problem, to manage the speed of execution — these largely belong here. The domain of luck is the opposite: results vary wildly even under identical conditions, and timing you can't control, a competitor's mistake, or the market's accidental drift decides the outcome instead. The trouble is that a single success bundles the results of both domains together, and after the fact, there's no clean way to pull them apart.

So the practical question has to change. Not "what caused this result," but "would this decision have been right again, had it been made under the same conditions." The first question builds a story backward from a result that's already happened. The second asks about the quality of the decision itself, separated from the result.

In practice, that question stays alive through two habits.

• **Record the moment of the decision.** Before you know the outcome — at the moment you're deciding — write down briefly how likely you think this judgment is to be right, and on what grounds. Memory gets rewritten to fit the result once you know it. A written record does not.
• **Imagine the failure before you decide.** Ask in advance: if this decision turned out to be a failure six months from now, why would that be? If the answer comes easily, the decision leans heavily on luck. If it's hard to find an answer, the decision leans closer to the domain of skill.

Sketching the path to failure before the outcome exists runs in exactly the opposite direction from the habit of assembling a story of success after the fact.

The Habit of Doubting the Story

This is where a life that uses luck and a life used by luck diverge. A life used by luck takes a single accidental result as proof of destiny, and stacks the next decision on top of that proof. It comes to believe an unrepeatable formula is repeatable, keeps repeating it, and when luck stops cooperating, the whole belief collapses. A life that uses luck, by contrast, sets aside luck's share of the credit even when the result is good — and turns that question into a habit, every time.

This distinction isn't a rhetorical gesture toward humility. There's a practical reason behind it. Someone who accurately sees luck's share doesn't grow overconfident after success and doesn't collapse after failure, because they can separate the quality of a decision from the size of its result. Someone — or some organization — unpracticed at this distinction mistakes the decision-making style of a lucky period for skill, keeps pushing it, and when luck turns, can't even understand why everything fell apart.

This habit requires no mysterious talent. What it requires is the persistence to keep asking one uncomfortable question: is the confidence I feel right now coming from a repeatable principle, or is it an optical illusion produced by a single coincidence? The moment a story wants to complete itself is exactly the moment to ask that question.

Go back to the two stories we started with. Whether the two people who happened to meet were truly fated, whether that founder was truly a born genius — neither can ever be confirmed. Accepting that it cannot be confirmed is the first condition of a life that uses luck rather than being used by it. The moment we believe we've confirmed the unconfirmable, we hand the next decision over to a story. The person who accepts that impossibility, by contrast, prepares the next decision a little more humbly — even while standing in front of that very same success.

Luck writes the headline. Skill writes the rest of the story.