View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  DevOps Blameless Postmortem |  Agile Start Stop Continue |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | 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. | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Low | Medium | Low | Low |
Timedifferent | 20-45 min | 30-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-12 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Postmortem Doc, Action Items, Timeline | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | LearningOperationsImprovement | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |