The Success Genome

Coded biographies · every claim sourced

How They
Made It

Success has many ingredients. Some you can build or choose for yourself; others you were born with and can't change. We read every person here against the same markers — the money behind them, who they knew, what they'd studied, and how far they'd fall if it went wrong — not to hand you a map of what you can or can't do, but so you can see clearly what you're up against, plan for it, and succeed anyway.

65
lives coded
11
made it the hard way, kept ownership
17
started on the softest ground
READ FIRST

Everyone here made it, and that's the catch. Plenty of people started in the same place and didn't, and they don't show up in any dataset. You're only looking at the ones who came out the other side.

Why the stories mislead

When someone successful tells their own story, they talk about the choices they made. The leap, the long hours, ignoring the people who said no. What they usually skip is the conditions they had going in: the parents who could float them through a bad year, the classmate who made an introduction, the timing that happened to line up. Often it isn't dishonesty. Those advantages were invisible to the person who had them, the way a fish doesn't notice the water. But it leaves you with a how-to guide built from half the story.

So you follow it, and when it doesn't work the easy conclusion is that the problem was you. Not enough grit, not enough talent, not enough nerve. That's the real harm. You end up wondering why it looked so easy for them, without ever seeing the head start that never made it into the story. This site tries to add it back.

To be clear, a head start doesn't guarantee anything. These people still built the companies, wrote the songs, and made the calls, and plenty of others who started with the same advantages went nowhere. The goal here isn't to explain away what they did or take anything from it. It's just to be honest about what they were working with, so you're not measuring yourself against a version of events that left out half the picture.

The survivors are the sample

hits on survivors reinforce here

During World War II, the US military looked at bombers coming back from missions to decide where to add armor. The returning planes were covered in bullet holes on the wings, the body, and the tail, so the obvious plan was to reinforce those spots. A statistician named Abraham Wald pointed out the mistake: put the armor where the returning planes had no holes, on the engines and the cockpit. Planes hit there hadn't made it back to be counted. The damage on the survivors only showed where a plane could take a hit and still fly home.

A success story is one of the planes that came back. The things that would have sunk the whole attempt, like having no cushion, no useful contacts, or no room for a second try, are exactly what you don't hear about, because the people who lacked them mostly didn't get far enough to write a book or give a talk. The same moves that worked for the people here were tried by plenty of others who lost, and none of them are in any dataset. There's no way to show you that missing group. The most this can do is point at the parts of the story that usually go unsaid.

How to read a record

Everyone gets two scores that people tend to lump together. Cost of failure is about money: the cushion that would have caught them if things fell apart. Headwinds is about identity: the bias and closed doors tied to race, gender, immigration, and disability. They're kept apart so the same disadvantage doesn't get counted twice. A poor white man can score high on cost of failure and low on headwinds, and a wealthy woman is often the reverse. On each page, the sections are tagged with the score they feed. Both are 0-to-10 calls made by hand from the sourced facts, not a formula. The method page walks through the reasoning.

Everything else, from money and connections to schooling, upbringing, and timing, is laid out with sources, so you can judge for yourself which advantages did the work instead of trusting the neat version of events.