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 |  DevOps Game Day |  Agile 4Ls Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | 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. | 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 | Low | High | Low | Low |
Timedifferent | 5-15 min | Halber Tag | 45–75 min | 20-45 min |
Participantsdifferent | 1-5 | 5-20 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Simulation Notes, Gaps List, Updated Runbooks | 4Ls Board, Learning Themes, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | StartupValidationCompetition | ResilienceOperationsIncident | RetrospectiveLearningReflectionTeam | LearningOperationsImprovement |