Build a personal library of failure post-mortems

Deliberately collect, read, and learn from failure case studies in your domain.

Why it works

Success cases teach you how one path to success looked — a thin signal given the survival filter. Failure post-mortems, by contrast, carry dense information about mechanisms: the specific decisions, assumptions, and dynamics that reliably lead to bad outcomes. Because the survivorship filter makes failures invisible by default, deliberately curating them is the counterweight that gives you access to the full distribution of what happens.

How to do it

1. For your industry or domain, actively find post-mortems: startup failure analyses, project retrospectives, research on what goes wrong.
2. For each one, extract: what assumption failed, what was missed, what signal was available but ignored?
3. Build a reference file you can consult when planning similar work.
4. Before launching any significant project, review the relevant failure patterns in your file.

Evidence

Failure case analysis is standard practice in aviation, medicine, and nuclear safety — domains where learning from failures systematically is a safety requirement. The rationale is directly tied to countering survivorship bias: mandatory reporting of failures makes the non-surviving cases visible. (clinical)

The value of failure libraries is well established in safety-critical industries; transfer to business and personal decision-making contexts is principled but the direct outcome evidence is thinner.

Common mistake

Reading failure cases and extracting only obvious errors ("they ran out of cash") rather than the subtler, structural decisions that compounded into those terminal failures.