View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Domain Storytelling |  Operations Process Mapping |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. | 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-2 h | 1-2 h | 1-3 h | 20-45 min |
Participantsdifferent | 1-8 | 2-8 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Domain Story, Glossary Notes, Process Narrative | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | KnowledgeDomain-Driven DesignProcess | ProcessOperationsImprovement | LearningOperationsImprovement |