This independent method study examines Seveneves through Fault Tree Analysis. It is an interpretation of the publisher's premise, not a claim that the fictional characters used this management method.
Verified premise
After a catastrophic event, humanity works to survive in orbital habitats under severe time and resource pressure.
Management thesis
Seveneves makes shared dependencies in survival infrastructure visible: redundant components can fail together when they rely on one support system.
System map
- Authority: Leaders set priorities, but engineers and crews observe failures first.
- Information: A review needs an event timeline rather than only the official summary.
- Resources: Severe constraints make every lost lesson costly.
- Incentives: Success can encourage repeating a fragile workaround without examining why it worked.
- Adaptation: A fault tree would expose shared infrastructure dependencies across apparent redundancy.
Apply the method
- Define the top event and system boundary precisely.
- List immediate causes and connect them with justified AND or OR logic.
- Decompose branches until basic events can be observed or tested.
Failure mode
Drawing only component failures while ignoring shared power, human response and unknown modes; inventing precise probabilities.
Ethical cost
A useful analogy must still identify whose voice, rights or exposure to harm the method could hide.
Limits of the analogy
A fictional megacrisis cannot supply real reliability data; a fault tree requires engineering verification.
Discussion question
Which assumption in this fictional system would you test before using the method in your own organisation?