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 Process Mapping |  Knowledge Modeling Domain Storytelling |  Domain Modeling Context Map |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 1-3 h | 20-45 min |
Participantsdifferent | 3-10 | 2-8 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | LearningOperationsImprovement |