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 |  Facilitation Expectation Mapping |  Operations A3 Problem Solving |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 20-45 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Expectation Map, Alignment Notes, Agreements | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LearningOperationsImprovement | AlignmentStakeholdersTeam | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
