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 Runbook |  DevOps Incident Command |  Business Strategy 5-Minuten VC-Check |  DevOps Game Day |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 20-60 min | As needed | 5-15 min | Halber Tag |
Participantsdifferent | 1-4 | 4-15 | 1-5 | 5-20 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Runbook, Checklist, Escalation Path | Incident Log, Action Tracker, Stakeholder Updates | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | OperationsReliabilityDocumentation | IncidentOperationsReliability | StartupValidationCompetition | ResilienceOperationsIncident |