Managing Unmanageable Complexity
summary
A concrete pitch: simple checklists prevent errors and speed recovery. Johns Hopkins cuts central line infections from ~11% to near zero, saving lives and ~$2M; the WHO’s 19-step surgical checklist lowers major complications 36% and deaths 46%; aviation checklists tame Boeing’s once-unflyable Model 299. Practical software checkpoints include before submitting a pull request, reviewer read‑every‑line rules, and a before deploying rollout-and-rollback plan with who watches what and how to verify success. Start small, iterate, and specify who does each step.
AI-written summary · about
chapters (7)
- 0:00Start
- 14:3610 Day Line-Infection Rate
- 21:30Why Checklists Work
- 24:40Before Submitting a Pull Request
- 25:54When Reviewing a Pull Request
- 26:50Before Deploying
- 30:15Patrick Joyce
related talks
33mPilots, Surgeons & Developers - Improving AppSec With Checklists
46mManaging The Process
41mLessons from Mission-Critical Systems in Fast-Moving Industries
28mChange management (Keep it Simple, Stupid!)
41mContinuous delivery in 10 easy mistakes
30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and Planning
44mEnhancing the Performance of Engineering Teams
38mSimplicity: The Key to Software Success