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 5-Minuten VC-Check |  Operations Learning Review |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Halber Tag | 5-15 min | 1-3 h | 45–75 min |
Participantsdifferent | 5-20 | 1-5 | 3-10 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Learning Review Notes, System Factors, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | StartupValidationCompetition | LearningRetrospectiveIncidentOperations | RetrospectiveLearningReflectionTeam |