2026-08-24
Link: https://how.complexsystems.fail/
HN Discussion: 1 points, 0 comments
This is Richard Cook's classic 18-point treatise on how complex systems fail — a short document that has quietly influenced two decades of thinking in SRE, aviation safety, healthcare, and incident response. If you've ever read a Google SRE book, an Etsy post-mortem, or anything John Allspaw has written on resilience engineering, you've absorbed ideas that trace back here. It deserves a permanent bookmark from anyone who operates production systems.
The premise is deceptively simple. Cook, an anesthesiologist and safety researcher, argues that in any sufficiently complex system:
What makes this document particularly valuable for a technical audience today: the language of "root cause analysis" is still ubiquitous in incident tooling, PagerDuty templates, and engineering culture, yet Cook explains precisely why that framing produces worse outcomes than a systems view. Teams that internalize this shift from asking "who broke it?" to "what pressures made this failure mode inevitable?" — and end up with post-mortems that actually change organizational behavior instead of assigning blame.
The whole thing is roughly 4 pages. You can read it in ten minutes. It will change how you write incident reports for the rest of your career. It's been cited in academic literature, referenced in Nicole Forsgren's DORA research, and quoted at practically every SRECon — yet it consistently gets rediscovered because there is no better distilled statement of the ideas.
The fact that this landed on HN with a single upvote is the sort of thing that makes you question the whole ranking algorithm.
