View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  DevOps Game Day |  Business Strategy Three Horizons |  DevOps Incident Command |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30-60 min | Halber Tag | Halbtags-Workshop, dann iterativ | As needed |
Participantsdifferent | 1-5 | 5-20 | 3-12 | 4-15 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Simulation Notes, Gaps List, Updated Runbooks | Horizon map, Portfolio view, Initiatives per horizon, Resource plan | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | PrioritizationOperationsPortfolio | ResilienceOperationsIncident | StrategyInnovationPortfolioForesight | IncidentOperationsReliability |