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 | ![]() Innovation Lean Startup | ![]() 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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 | Medium | Low | Low |
Timedifferent | 30-90 min | Wochen bis Monate je Lernzyklus | 45–75 min | 30-60 min |
Participantsdifferent | 3-12 | 2-8 | Team members involved | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | LeanStartupValidationMVP | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |



