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 Domain Storytelling |  Knowledge Modeling Concept Mapping |  Operations Process Mapping |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 1-2 h | 1-2 h | 1-3 h | 2-4 h Analyse, laufend |
Participantsdifferent | 2-8 | 1-8 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Concept Map, Relationship Labels, Knowledge Gaps | Process Map, Handoff List, Improvement Backlog | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | KnowledgeConceptsMappingSensemaking | ProcessOperationsImprovement | OperationsConstraintsFlowImprovement |