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 Blameless Postmortem |  Business Strategy 5-Minuten VC-Check |  Agile 4Ls Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-90 min | 5-15 min | 45–75 min | 30-60 min |
Participantsdifferent | 3-12 | 1-5 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | StartupValidationCompetition | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |