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 |  Operations Gemba Walk |  Knowledge Modeling Domain Storytelling |  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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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 | Low | Medium |
Timedifferent | 20-45 min | 30-120 min | 1-2 h | 45-90 min |
Participantsdifferent | 3-12 | 2-6 | 2-8 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas | Domain Story, Glossary Notes, Process Narrative | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LearningOperationsImprovement | LeanObservationProcessOperations | KnowledgeDomain-Driven DesignProcess | LeanProblem solvingCoachingOperations |