Purpose
The method helps clarify incident work, roles, and countermeasures concretely. It aligns incident picture, responsibilities, and next countermeasures. The outcome is captured as simulation notes, gap list, and updated runbooks.
DevOps
Game Day
Turns incident work, roles, and countermeasures into a tangible result by selecting a scenario, preparing environment and rules, and improving runbooks.
How do system, tools, and team react to realistically injected failures, and which gaps in runbooks, monitoring, or roles become visible?
HighWorkshopHalber Tag
How it works
The team follows the steps: choose a scenario, prepare environment and rules, run a simulation, observe response and gaps, and improve runbooks. Each step is captured visibly. At the end, simulation notes, gap list, and updated runbooks are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Choose scenario
- 2Prepare environment and rules
- 3Run simulation
- 4Observe response and gaps
- 5Improve runbooks
The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Resilience Testing
- Incident Preparedness
- Operations Training
Not good for
- Teams without baseline runbooks
- Unprepared live systems
Deep dive
In detail
Game Day follows a clear working logic: choose a scenario, prepare environment and rules, run a simulation, observe response and gaps, and improve runbooks. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, simulation notes, gap list, and updated runbooks are produced and ready to support decisions, learning, or further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about half a day with 5-20 participants and use the format in a facilitated workshop. The method is complex and should be prepared carefully; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Output artifacts
Simulation NotesGaps ListUpdated Runbooks
Artifact templates
Game Day Working TemplateCompact working template for Game Day with context, input, output artifacts, and next step.markdown
Game Day Working TemplateCompact working template for Game Day with context, input, output artifacts, and next step.
markdowngame-day-working-template.md
Compact working template for Game Day with context, input, output artifacts, and next step.
Game Day Working Template
Goal
A realistic exercise to practice incident response and recovery.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Simulation Notes:
- Gaps List:
- Updated Runbooks:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Failure Scenario Analysis
Statt Game Day, wenn du Ausfallszenarien vorab analysieren willst, ohne den Ernstfall praktisch zu simulieren.
Similar methods
All methodsDevOps
ChatOps
Turns incident work, roles, and countermeasures into a tangible result by integrating tools, routing alerts, and improving the workflow.
DevOps
Incident Command
Turns incident work, roles, and countermeasures into a tangible result by declaring an incident, assigning commander and roles, and closing and reviewing the incident.
DevOps
Blameless Postmortem
Turns incident work, roles, and countermeasures into a tangible result by documenting the incident, describing impact and timeline, and sharing learnings.
DevOps
Incident Timeline Analysis
Turns incident work, roles, and countermeasures into a tangible result by collecting sources, ordering events chronologically, and deriving lessons and actions.
Operations
Runbook
Turns workflows, data, causes, and improvements into a tangible result by defining a scenario, writing steps, and testing and updating.
Operations
Learning Review
Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and stance, reconstructing the timeline, and deriving learning actions.