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 |  Knowledge Modeling Feynman Technique |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-45 min | 20-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-12 | 1 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Plain-language Explanation, Knowledge Gaps, Study Notes | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningOperationsImprovement | LearningKnowledgeUnderstanding | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |