View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy 5-Minuten VC-Check |  Operations Runbook |  DevOps Game Day |  DevOps Blameless Postmortem |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 5-15 min | 20-60 min | Halber Tag | 30-90 min |
Participantsdifferent | 1-5 | 1-4 | 5-20 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Runbook, Checklist, Escalation Path | Simulation Notes, Gaps List, Updated Runbooks | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | StartupValidationCompetition | OperationsReliabilityDocumentation | ResilienceOperationsIncident | Site Reliability EngineeringIncidentLearningReliability |