View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Operations After-Action Review |  Operations Process Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 20-45 min | 1-3 h |
Participantsdifferent | 2-8 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Lessons learned, Action items, Event summary | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | LearningOperationsImprovement | ProcessOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
