Encyclopedia · Free preview
Normal Accidents Theory (Perrow)
Charles Perrow's seminal insight: in systems that are both complex (many non-linear interactions) and tightly coupled (processes happen fast with little slack), catastrophic failures are inevitable—'normal'—regardless of how competent the operators are or how many safety systems are in place. The theory emerged from analysis of Three Mile Island but applies to financial markets, air traffic control, nuclear weapons systems, and modern software infrastructure. Two properties create normal accidents: interactive complexity (components interact in unexpected and invisible ways) and tight coupling (when something goes wrong, the cascade is too fast for human intervention). The critical insight: these systems cannot be made safe through adding more safety layers, because the safety layers themselves add complexity and create new interaction possibilities. Each 'fix' potentially introduces new failure modes. The implication is disturbing: some systems can only be made safe by being made simpler or more loosely coupled, not by adding safeguards to their current architecture.
When to use it
When designing or evaluating safety in complex systems. When investigating system failures. When deciding whether to add complexity to an already complex system. When the proposed safety solution adds more moving parts to an already complex system.
How it can help
Provides a framework for assessing whether a system is in the 'normal accident' zone (high complexity + tight coupling) where catastrophe should be expected, not just feared. Diagnostic: map your system on Perrow's two-by-two matrix of complexity (linear vs. complex interactions) and coupling (loose vs. tight). If you're in the complex-tight quadrant, understand that no amount of procedures, training, or safety systems will prevent eventual failure. The only structural solutions: (1) reduce coupling by adding buffers, slack, and circuit breakers, (2) reduce interactive complexity by modularizing systems with clean interfaces, (3) prepare for failure (resilience) rather than trying to prevent it (robustness). For any catastrophe investigation, ask: was this a normal accident (systemic) or a human error (individual)?
Keep exploring
Read the full page.
Create your free access to continue reading and explore the complete library.
Register free with ChatGPT →Already registered? Use the same button to sign in.
Sign-in shares your email with Michael Simmons to create your site access. No payment required. Newsletter signup is separate. How your data is used