Embracing the Multi-Party Dilemma: Incident Response Across...
summary
Over a dozen deep case analyses from 2021 use thematic incident analysis (Adaptive Capacity Labs method) to show a repeatable pattern: information and impact asymmetry, hidden transitive dependencies, high coordination cost and mission/tempo misalignment across vendor boundaries. Concrete wins include using early imperfect vendor signals to escape impact faster and joint config changes with a CDN vendor that reduced blast radius; failures include lost debugging data when a customer restarted a DB cluster. Recommended fixes: pick key vendors, capture incident trace data, and adopt bidirectional engineering-level information sharing and joint rehearsals.
AI-written summary · about
chapters (11)
- 0:00Multi-party dilemma intro
- 3:10Defining the dilemma pattern
- 7:20Dilemma from incident analysis
- 12:39Challenges at org boundaries
- 17:15Coordination costs and misalignment
- 21:52Bidirectional info flow
- 25:02Third-party expertise challenges
- 28:59Dilemma recap and consequences
- 31:03Dilemma solutions with vendors
- 34:16Next steps and research
- 36:02Acknowledgements
related talks
35mEffective Handling of Third-Party Supplier Incidents
17mIncident Response @ Scale-Building a Next Generation SOC
46mReducing Incident Scope. Practical Case Studies
45mFailure Happens: Improving Incident Response in Large-Scale Organizations
15mIncident Ready: Chaos Engineer Your Incident Response
31mFuturistic Luxury Incident Response
28mRevolutionizing Incident Response
39mNavigating the Chaos: A Holistic Approach to Incident Management