Fake It 'Til You Make It: Get the Most out of Incident Simulations
summary
Run timeboxed (e.g., 90 minutes), realistic mock incidents that are designed to fail on purpose so gaps surface: use a facilitator, responders, silent observers and a scribe; map real tools into sandboxed environments and clearly label them to avoid accidental production changes. Keep the clock running—don't stop the clock—and drop scripted curveballs if the scenario runs too smoothly. Finish with a good/bad/ugly retro, assign owners and short deadlines for action items, and track fixes in your ticket system.
AI-written summary · about
chapters (10)
- 0:00Introduction to incident simulations
- 3:18Why run incident simulations
- 5:28Designing effective simulations
- 10:07Crafting realistic scenarios
- 13:14Assembling the right team
- 16:05Setting up the simulation environment
- 17:54Running the simulation
- 19:42Conducting the retrospective
- 23:13Improving future simulations
- 24:57Q&A session
related talks
15mIncident Ready: Chaos Engineer Your Incident Response
33mGames We Play to Improve Incident Response Effectiveness
46mGames We Play to Improve on Incident Response
40mBecoming a Gamemaster: Designing IT Emergency Operations and Drills
30mHow to have an operational incident a crash course
30mIncident Groundhog Day
05mMayday, Mayday: Starting a job w/ a production incident
01h 08mWorkshop: Run your first game day