Managing Misfortune for Best Results
summary
Describes a weekly outage training game called wheel of misfortune with a “victim” (next on-call), a dungeon master who drives the scenario, a scribe, and observers; typical slot is an hour but scenarios finish in 30–40 minutes. Uses real monitoring time links and binary crash tombstones to debug: example shows SLA dipping from 99.9% to ~90% and ~50 correlated crashes per minute from a test job; recommends split roles (driver vs decision maker), playbooks, post‑game transcription, and calibrated stress levels.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:19Name of the game
- 1:29Mechanics
- 2:42Why would you run Outage Training RPGs?
- 4:20Aside - Project Aristotle - Analysis of Effective teams
- 6:45Goals
- 8:01'The Triar
- 9:25The Trial antidote
- 9:36The Trial. antidote
- 9:58The Kobayashi Maru test
- 10:38Kobayashi Maru test - antidote
- 12:05"The Spotlight". Antidote 2
- 12:27Doing it wrong 14 - Brave Sir Robin Ran Away
- 12:43Brave Sir Robin Ran Away - antidote
- 12:58Scenario selection
- 13:57Cross team exercises
- 15:28Links to monitor for incidents
- 16:37Playbook of useful aulages
- 18:07Session log and debrief
related talks
45mLet's play a real life Dungeon and Dragons
22mDon’t wait for an outage to improve your reliability
20mChaos: breaking your systems to make them unbreakable
31mThe Art of Turning Incidents into Opportunities
30mIncident Groundhog Day
30mFake It 'Til You Make It: Get the Most out of Incident Simulations
40mBecoming a Gamemaster: Designing IT Emergency Operations and Drills
45mWhat to do when complex systems fail: A guide to chaos management