Of Course It Went Right / Why This Was Never an Accident

When Improbable Outcomes Keep Happening

Repeated success is often labelled as luck, which hides preparation and design.

10 min read

When Improbable Outcomes Keep Happening

Category: Why This Was Never an Accident Repeated success is often labelled as luck, which hides preparation and design.


There is a rugby club, mid-table and unglamorous, that has developed an irritating habit. They win in the last ten minutes. Not always — they lose plenty — but when a match is close and the clock is red, they are the side that scores. The commentators have a phrase for it now, the way commentators always do. They are a “lucky” team. They “find something at the death.” They “get the rub of the green when it counts.” It is said warmly, and it is meant as a compliment, and it is almost entirely wrong.

Because here is the thing about the last ten minutes of a rugby match: it is not a separate game played by the fairies of fortune. It is the same game, played by men whose legs have stopped working. The team that scores at the death is, overwhelmingly, the team that can still run at the death — the team whose forwards can still hit a ruck with intent when their lungs are burning, whose decision-making hasn’t degraded into hopeful kicks, whose substitutes were brought on at exactly the right minute to be fresh for exactly this moment. None of that is luck. It is conditioning, and bench management, and a coach who built the entire training week around the brutal, unfashionable premise that matches are won in the part of them everyone else is too tired to contest.

So when the same team finds the same late winner for the fourth season running, something has quietly gone wrong with the word “lucky.” A lucky bounce is luck. A lucky bounce that keeps arriving for the same side, in the same phase of the game, year after year, is not luck. It is a machine, and the machine has been built on purpose by people who decided that the most improbable-looking part of the match was the part most worth preparing for.

The trouble is that the machine is invisible, and the bounce of the ball is not. So we credit the bounce.


The Principle

One improbable good outcome is luck. The same improbable good outcome, recurring around the same person or team, is a system — and calling it luck is a failure of observation that hides the preparation, judgement, and design quietly manufacturing the odds.

Luck is real, and it matters, and pretending otherwise is its own kind of stupidity. A single fortunate outcome may genuinely be fortune: the right break at the right moment that no one earned and no one could have engineered. The mistake is not in believing in luck. The mistake is in keeping the explanation after it has stopped fitting the evidence — in watching the improbable happen again, and again, and again, to the same people, and reaching once more for the word that explains a one-off.

Repetition is the tell. Luck, by its nature, does not have a favourite. It does not reliably attend the same team in the same situation season after season. The moment a “lucky” outcome starts recurring with a pattern to it — the same phase, the same kind of moment, the same hands — you are no longer looking at chance. You are looking at something that produces the outcome, and the only honest question left is what that something is. The skill the principle asks for is a small, awkward one: to stop saying “lucky again” and go and find the machine.

Why It Is Inevitable

The mislabelling happens reliably, for reasons that have nothing to do with anyone being foolish.

The first is that the outcome is loud and the preparation is silent. The late winner is on the television; the four hundred extra conditioning sessions that made it possible are not. We explain what we can see, and what we can see is the bounce of the ball, not the lungs that were trained to still be working when it bounced. The visible event crowds out the invisible cause, every time, unless someone deliberately goes looking for the cause.

The second is that good design is built precisely to look effortless. The whole point of preparation is that, when the moment comes, it does not look like effort — it looks like ease, like instinct, like the thing simply going right. A well-run handover that prevents a disaster produces no disaster, which is to say it produces nothing visible at all. The better the system, the more it erases its own footprints, and the more its results look like things that just happened to happen.

The third is more human and less flattering. Calling someone else’s repeated success “luck” is comfortable, because the alternative is to admit they did something you didn’t, or saw something you missed, or grafted at something you found too boring to grind at. “They got lucky” asks nothing of us. “They built something” asks us to go and find out what, and possibly to do it ourselves. So the lazy explanation has gravity. It lets the observer off the hook and lets the achiever’s actual work stay invisible, which suits a surprising number of people on both sides.

And so the same scene replays. Improbable good thing happens to the same people once more; everyone reaches for “lucky”; nobody goes looking for the machine; the machine, undisturbed, keeps running. It is inevitable not because people are dim but because the cheap explanation is always closer to hand than the true one.

How It Shows Up

  • The same person or team is “lucky” with the same kind of thing, repeatedly — late results, well-timed decisions, near-misses that turn out fine — and the specificity of the pattern is never treated as suspicious.
  • The successes look effortless from outside, which is taken as evidence they were easy rather than as evidence they were well-prepared.
  • The preparation that produced them is invisible because it happened earlier, elsewhere, and produced no drama at the time.
  • The word “lucky” is used admiringly and constantly, and nobody asks the obvious follow-up: how, exactly, does the same luck keep finding the same door?
  • Competitors who lose to the pattern explain it away rather than dismantling it — which guarantees they keep losing to it.
  • The people inside the machine often don’t correct the “lucky” label, either out of modesty or because they’ve half-believed it themselves, and so the design stays uncredited even by its builders.

Why It Causes Benefit

Refusing the lazy “lucky” and going to find the machine is, quietly, one of the most valuable habits a person or an organisation can have — and it pays off twice.

The first payoff is that you can copy a machine. You cannot copy luck. If a rival’s repeated success is genuinely fortune, there is nothing to learn and nothing to do but wait for the dice to turn. But if it’s a system — and when it recurs, it almost always is — then it can be studied, understood, and rebuilt. Every “they just got lucky again” is a refusal to learn something that was sitting in plain sight, available to anyone willing to look past the bounce of the ball. The person who insists on finding the machine is handing themselves an education that everyone shouting “lucky” has declined.

The second payoff is that you can build one. Once you accept that improbable good outcomes are manufacturable — that the late winner is a conditioning programme wearing a disguise — you stop treating success as weather and start treating it as engineering. You ask which improbable-looking outcome you’d most like to have happen reliably, and then you ask what would have to be true, upstream and unglamorously, for the odds to bend your way. That is the whole thesis of taking success seriously: not that you can guarantee any single outcome, which you can’t, but that you can quietly load the dice across many of them until “lucky” becomes your most frequent verdict — at which point you, too, will be called fortunate by people who haven’t bothered to look.

This is the engine room of the entire idea that success is never an accident. The recurring improbable win is the clearest possible proof of it, because chance does not repeat with a pattern and design does. Every time you decline the word “lucky” and find the machine instead, you collect another piece of evidence that the good outcomes worth having are built, not bestowed — and you learn a little more about how to build your own.

How To Cultivate It

  • When you catch yourself calling a repeated success “lucky,” treat that word as an alarm rather than an explanation. The fourth recurrence of a “fluke” is a standing invitation to go and find what’s actually producing it.
  • Look upstream and earlier. The cause of a visible late outcome almost never lives at the moment it appears — it lives in the preparation, the conditioning, the decision made calmly three steps before, the boring work done when no one was watching. Trace it back.
  • Be specific about the pattern. Don’t just note that someone keeps succeeding; note exactly what kind of success keeps recurring, in what situation. The specificity is the thread that leads to the machine, because a real system produces a characteristic shape of result.
  • Ask the manufacturing question directly: “If this were designed rather than lucky, what would the design be?” Then go and check whether that design exists. It usually does.
  • When the machine is yours, resist the urge to accept the compliment of “lucky.” Modesty that lets your own design stay invisible is not humility; it’s a failure to credit and protect the thing that’s actually working — and uncredited machines get cut.
  • Apply it to your own near-misses, not just your wins. The disaster that “luckily” didn’t happen was often prevented by a system you’ve stopped noticing. Find it before you decommission it by accident.

What Good Looks Like

A person or an organisation that has lost patience with the word “lucky” as an explanation for anything that has happened more than twice. When a rival keeps pulling off the improbable, they don’t shrug and envy the fortune — they go and reverse-engineer the machine, on the working assumption that recurrence means design. When they keep pulling off the improbable, they know precisely why, because they built it on purpose and can name the unglamorous upstream work that bends the odds. They understand the line that Terry Pratchett gave us — “Million-to-one chances crop up nine times out of ten” — not as a joke about a daft universe, but as a sharp observation about engineered ones: that the long-shot outcome arrives with suspicious reliability precisely when someone has quietly arranged for it to. They take their own successes seriously enough to credit the system behind them, and other people’s successes seriously enough to study rather than dismiss. And they hold the whole thing without arrogance, because they know the flip side perfectly well: the moment they stop maintaining the machine, the luck will desert them on schedule, and the bounce of the ball will go back to being just a bounce of the ball.

A Reflective Question

Think of the last time you described someone’s success — or your own — as “lucky.” If it has happened more than once, in more or less the same way, what would you find if you stopped explaining it with that word and went looking for the machine instead? And which is the more uncomfortable possibility: that there is no machine and it really was chance, or that there is one, and you’ve been declining to learn it?