View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Operations A3 Problem Solving |  Operations After-Action Review |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 20-45 min | 45–75 min |
Participantsdifferent | 3-12 | 2-5 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AlignmentStakeholdersTeam | LeanProblem solvingCoachingOperations | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam |