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 Gemba Walk |  Domain Modeling Context Map |  Decision Making OODA Loop |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-120 min | 1-3 h | 15-60 min je Zyklus | 20-45 min |
Participantsdifferent | 2-6 | 2-8 | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Observation Notes, Improvement Ideas | Context Map, Integration Patterns, Boundary Notes | Situation Assessment, Decision Loop, Action Updates | Lessons learned, Action items, Event summary |
Tagsno overlap | LeanObservationProcessOperations | Domain-Driven DesignBoundariesStrategy | DecisionChangeLearningStrategy | LearningOperationsImprovement |