View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Business Strategy Three Horizons |  DevOps Blameless Postmortem |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | Three Horizons helps clarify strategic options across different timeframes. It compares strengths, risks, market logic, and investment choices, and captures the result as a horizon map, portfolio view, and initiatives per horizon. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Halber Tag | Halbtags-Workshop, dann iterativ | 30-90 min | 20-45 min |
Participantsdifferent | 5-20 | 3-12 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Horizon map, Portfolio view, Initiatives per horizon, Resource plan | Postmortem Doc, Action Items, Timeline | Lessons learned, Action items, Event summary |
Tagsno overlap | ResilienceOperationsIncident | StrategyInnovationPortfolioForesight | Site Reliability EngineeringIncidentLearningReliability | LearningOperationsImprovement |