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 Alignment Mapping |  Facilitation Stakeholder Salience Model |  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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 60-90 min | 45–75 min |
Participantsdifferent | 3-10 | 4-12 | 3-6 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningRetrospectiveIncidentOperations | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance | RetrospectiveLearningReflectionTeam |