Gene Kranz, flight director during Apollo 13, said it plainly: failure is not an option. When the spacecraft was damaged and three astronauts faced suffocation, Kranz and his team treated every possible scenario as one they had to solve. No backup plan. No accepting defeat. Just relentless problem-solving until the crew came home.
That's the 1% doctrine in action. When the downside is catastrophic—loss of life, company collapse, career-ending failure—the probability doesn't matter. You mitigate anyway.
But here's the catch for project managers: most risks don't have Apollo 13 stakes. And treating every risk like it's existential leads to costly over-preparation or, worse, decision paralysis.
The short version
- The 1% doctrine applies to low-probability, catastrophic-impact risks
- Expected value = probability × impact; some risks warrant mitigation regardless of low probability
- Insurance works by shifting expected value between beneficiary and insurer
- Insurance fails when correlated failures eliminate independence across insured parties
- Project risks need judgment about which doctrine actually applies
Why Some Risks Get Treated Differently
Take two risks on a project. Risk A: your vendor might miss a deadline by two weeks. Impact: minor schedule slip. Risk B: the data center your infrastructure runs on has a small chance of catastrophic failure that wipes your production environment.
Risk A is manageable. You absorb the impact, adjust the timeline, maybe push the launch. Life goes on.
Risk B? Even at low probability, you don't roll the dice. You buy insurance. You build redundancy. You have a disaster recovery plan. You test it. The cost of mitigation feels high until you multiply it against what failure actually means.
This is the logic behind the 1% doctrine. When impact is catastrophic enough, expected value becomes material regardless of how small the probability looks.
The Insurance Trap
Here's where things get interesting. Insurance exists because beneficiaries and insurers see different expected values. The beneficiary faces a low-probability, high-impact event. The insurer aggregates across many clients. For any single client, the probability is low. For the pool, the impact is manageable. The premium bridges this gap.
Everyone sleeps at night. Until they don't.
Insurance breaks when the independence assumption fails. If all your clients face the same correlated risk—a global pandemic, a regulatory shift that affects an entire sector, a cloud provider outage—then the insurer's aggregate probability model collapses. Suddenly the insurer can't pay. The beneficiaries discover their "transfer" didn't actually transfer anything.
For project managers, this is a useful analogy. Are you relying on a single vendor's reliability? A single cloud region? A single person's knowledge? These look independent on paper. In reality, correlated failures happen.
Our analysis
The real skill in risk management is correctly categorizing which risks follow the 1% doctrine and which follow normal expected-value logic. Over-apply the doctrine and you spend mitigation budget on risks that don't justify it. Under-apply it and you get caught by the black swans you dismissed.
The trade-off is asymmetric: over-spending on mitigation is painful but recoverable; under-preparing for a true 1% event can be existential. This means the cost of false positives (treating normal risks as catastrophic) is lower than the cost of false negatives (missing a real catastrophic risk). That asymmetry should shift your default posture toward caution—but not paralysis.
Watch for false independence in your risk register. "Vendor A" and "Vendor B" look like separate risks until you realize they share the same parent company, the same data center, the same key person. When correlated failures strike, your diversification wasn't.
Risk Categorization Checklist
| Category | Question to Ask | Typical Response |
|---|---|---|
| Normal Risk | "If this fails, can we absorb and recover?" | Accept, monitor, plan response |
| 1% Doctrine Risk | "If this fails, does someone face serious harm?" | Mitigate regardless of cost |
| Correlated Risk | "Do our 'separate' risks share hidden dependencies?" | Consolidate and treat as one |
What to watch next
Audit your top five project risks this week. For each, ask: if this fails catastrophically, what happens? If the answer is "we adjust," manage it normally. If the answer is "we're in trouble," apply the 1% doctrine and invest in real mitigation. Also check whether your "independent" risks share hidden dependencies.
Key takeaways
- Categorize risks: normal expected-value or existential (1% doctrine)
- Don't over-invest in low-impact risks just because probability is low
- Insurance and vendor reliability create false independence assumptions
- Correlated failures break standard risk models
- The cost of over-preparing is lower than the cost of missing a true catastrophe
Frequently asked questions
How do I know if a risk deserves 1% doctrine treatment?
Ask what happens if the risk materializes. If the impact is catastrophic—career-ending, company-threatening, or safety-critical—the probability doesn't matter. Mitigate.
What does correlated failure mean for my project?
It means two "separate" risks can fail simultaneously because they share a hidden dependency: same vendor, same infrastructure, same person, same regulatory environment.
Is insurance always the right mitigation for low-probability risks?
Insurance works when failures are independent across the insured pool. If your risks are correlated—like depending on one cloud provider for everything—insurance may not protect you as expected.
How does the 1% doctrine apply to everyday project risks?
It doesn't for most of them. Most project risks have recoverable impacts. Save the doctrine for risks where failure means serious harm, not just schedule inconvenience.