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 |  Domain Modeling Context Map |  Systems Thinking Leverage Points |  Decision Making OODA Loop |
|---|---|---|---|---|
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 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 20-45 min | 1-3 h | Half day | 15-60 min je Zyklus |
Participantsdifferent | 3-12 | 2-8 | 3-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Context Map, Integration Patterns, Boundary Notes | Leverage Map, Action Strategy | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | LearningOperationsImprovement | Domain-Driven DesignBoundariesStrategy | Systems thinkingChangeStrategy | DecisionChangeLearningStrategy |