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 Learning Review |  Decision Making Force Field Analysis |  Operations After-Action Review |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 20-45 min | 45–75 min |
Participantsdifferent | 3-10 | 3-12 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Force Field Map, Change Levers, Risk Notes | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningRetrospectiveIncidentOperations | ChangeDecisionStrategy | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam |