View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Operations ABC Analysis |  Agile Start Stop Continue |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 30-60 min | 30-60 min | 20-45 min |
Participantsdifferent | Team members involved | 1-5 | 3-12 | 3-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | ABC Classification, Focus Rules, Control List | Start Stop Continue Board, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveLearningReflectionTeam | PrioritizationOperationsPortfolio | RetrospectiveImprovementTeamReflection | LearningOperationsImprovement |