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 |  Agile 4Ls Retrospective |  Facilitation Fishbowl Discussion |
|---|---|---|---|
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. | 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 controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-90 min | 45–75 min | 45-90 min |
Participantsdifferent | 3-12 | Team members involved | 8-80 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | 4Ls Board, Learning Themes, Improvement Actions | Discussion Insights, Observed Tensions, Follow-up Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveLearningReflectionTeam | FacilitationDialogueLarge group |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
