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 |  Decision Making Delphi Method |  Agile 4Ls Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 30-90 min | 1-4 Wochen | 45–75 min | 30-60 min |
Participantsdifferent | 3-12 | 6-30 Experten | Team members involved | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Expert Forecast, Consensus Range, Assumption Notes | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | ForecastingExpertsDecisionStrategy | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |