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 |  Agile 4Ls Retrospective |  Facilitation Responsibility Poker |  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. | 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-45 min | 45–75 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | Team members involved | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Emotion Board, Themes, Action Items |
Tagsno overlap | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam | RolesResponsibilityTeamFacilitation | RetrospectiveTeamReflection |