The Luck We Edit Out

I get suspicious when people don't credit luck.

When a product wins, we reverse-engineer the story. The roadmap choices, the positioning, the focus. And we land on a clean conclusion: this thing won because it was good. It's a satisfying story. It implies a meritocracy. Quality rises, mediocrity sinks, and the market is a fair judge.

We confuse outcomes with causes

Would Beethoven have been Beethoven if classical music hadn't peaked at exactly the moment he was alive to compose it? Would Amazon exist if consumer internet, logistics infrastructure, and digital payments hadn't all matured at precisely the right time? We look at these outcomes and say: genius. Vision. Execution.

Sure. But also: timing. Also: luck. Also: a world that happened to be ready.

We do the same thing with products. We look at what survived and assume it survived because it deserved to. But survivorship bias is brutal. The graveyard of excellent products that launched too early, or into the wrong market, or just slightly before the world was ready — it's enormous. We just don't talk about it, because there's nothing to write a case study about.

The data backs this up more than you'd expect. When CB Insights went through the post-mortems of failed startups, the single most-cited cause wasn't money or talent — it was building something the market didn't want yet, named in roughly 42% of cases.^[2] Marc Andreessen has put it more bluntly: most failed startups aren't bad ideas, they're good ideas with bad timing.^[3] The hard part isn't figuring out what the opportunity is. It's figuring out when.

The three things that actually have to converge

Product success isn't a single variable. It's closer to three variables that have to align at the same time:

The product has to be good enough — functional, usable, solving a real problem. But "good enough" is doing a lot of work in that sentence. It doesn't mean best-in-class. It doesn't mean most features. It means fit for the moment.

The market has to be ready to feel the pain. A product solving a problem people don't know they have yet is just an expensive experiment. A product landing on a market that's been bruised by the problem for years, desperate for relief — even an imperfect solution can look like a revelation.

The timing has to be right. This is the one we almost never credit. Timing determines whether the infrastructure exists to support your product. Whether cultural attitudes have shifted. Whether a competitor already owns the space or hasn't arrived yet. You can't manufacture timing. But it decides more than we like to admit.

How much more? Bill Gross, who founded the incubator Idealab and has launched well over 100 companies, once tried to figure out what actually separated his winners from his failures. He scored 200 companies — his own and others' — across five factors: the idea, the team, the business model, funding, and timing. He expected the idea to come out on top. It came in dead last. Timing was first, accounting for 42% of the gap between success and failure — more than the team, more than the business model, more than funding, and more than the idea.^[1]

When all three converge, you get a hit. When one is off, even great work disappears.

What this should change about how we build

Be humble about wins. When something works, ask: would this have worked two years ago? In a different market? If a competitor had moved six months faster? If the answer is "probably not," then the product was just one ingredient. Don't let success convince you that you've cracked a code you haven't.

Be generous about failures. Teams that shipped something that didn't find traction aren't automatically incompetent. They might have just shown up early to a party that wasn't ready to start yet. The same idea, five years later, in a market that's finally ready — that's how a lot of billion-dollar companies got built.

Ask harder questions before you build. Not just is this a good product? but is this the moment? Is the market feeling the pain acutely enough? Is the infrastructure there? Has enough changed that people will actually care? Those questions are harder to answer than roadmap questions. But they matter more.

The edit we keep making to success stories

When products win, the story gets cleaned up. The luck gets removed. What's left is a tight narrative about vision and execution — and that narrative gets turned into a framework that other teams try to replicate.

But you can't replicate timing. You can only read it. You can watch markets carefully, notice when pain is building, and ask whether the moment is coming. That's not the same as manufacturing luck — but it's a lot more honest than pretending luck wasn't involved.

I'll go first: some of the best work I've been a part of succeeded because the timing was right. We did good work. But we were also in the right place at the right time.

So the next time a product wins — yours or someone else's — resist the clean story. Ask what the world looked like the day it launched. Ask who else tried this and got buried for being three years early. Ask whether the same team, with the same product, would win again starting today. If you can't say yes with a straight face, then it wasn't just good. It was good and it was time. And that's the hard part: when you're winning, being good and being lucky feel exactly the same.