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 |  Facilitation Expectation Mapping |  Agile Starfish Retrospective |  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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-10 | 3-12 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Expectation Map, Alignment Notes, Agreements | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningRetrospectiveIncidentOperations | AlignmentStakeholdersTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |