THE COMPARISON ROOM
Put the patterns side by side.
Choose up to four cases. Compare what happened, then ask which similarities are meaningful and which depend on context.
Silicon Valley Bank: concentrated confidence
NASA / Space Shuttle ChallengerFacebook / Meta
| Dimension | EXHIBIT 001Challenger: when warnings weren’t enough | EXHIBIT 002Facebook: a network that took itself offline |
|---|---|---|
| Industry | EngineeringInspect evidence | IT & softwareInspect evidence |
| Organization | NASA / Space Shuttle ChallengerInspect evidence | Facebook / MetaInspect evidence |
| Year & location | 1986 · United StatesInspect evidence | 2021 · GlobalInspect evidence |
| Organization size | LargeInspect evidence | LargeInspect evidence |
| Failure type | Safety barriersInspect evidence | Deployment failureInspect evidence |
| Warning signs | Engineers raised concerns about the effect of low temperatures on booster-joint seals before launch. Inspect evidence | The detailed postmortem reports that a bug in an auditing tool failed to stop the command responsible for the outage. Inspect evidence |
| Decision pattern | Failure to escalateInspect evidence | Coupled dependenciesInspect evidence |
| Decisions & incentives | The launch was approved after a review process that did not carry engineering concerns to all key decision-makers. Inspect evidence | A command during backbone maintenance disconnected the data centers; dependent DNS and recovery tools were affected. Inspect evidence |
| Assumptions | Museum analysis: prior flights without catastrophe could be treated as stronger evidence of safety than they actually provided.Inspect evidence | Museum analysis: recovery tools can appear independent while relying on the infrastructure they are meant to repair.Inspect evidence |
| Technical & organizational factors | The Rogers Commission identified failure of the right solid rocket booster’s pressure seal. It also found communication failures and a decision process based on incomplete or misleading information. Inspect evidence | Facebook’s postmortem attributes the disruption to a backbone configuration change. The outage also affected internal systems and complicated recovery. Inspect evidence |
| Consequences | All seven crew members died. Families, colleagues, students, and the wider public were affected. Inspect evidence | People and businesses lost access to services. The company said it had no evidence of compromised user data from the outage. Inspect evidence |
| Recovery | Booster hardware was modified and tested; shuttle flights resumed in September 1988. Inspect evidence | Services were restored; the organization described work to improve infrastructure resilience. Inspect evidence |
| Analytical frameworks | Swiss Cheese Model · Normalization of deviance · Systems thinkingInspect evidence | Fault Tree Analysis · FMEA · Systems thinkingInspect evidence |
| Preventive actions | Give unresolved safety objections a documented path to an independent decision-maker, and require positive evidence for operation outside a tested envelope.Inspect evidence | Test an out-of-band recovery path with production routing, DNS, and identity services deliberately unavailable.Inspect evidence |
A SHARED LENS
Systems thinking
Compare the ownership of warning signals, the independence of safeguards, and the assumptions behind recovery. A shared framework is a starting point for questions, not evidence that these events had the same cause.