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 Event Modeling |  Knowledge Modeling Concept Mapping |  Operations 8D Problem Solving |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 2-6 h | 1-2 h | 1-6 Wochen | 1-2 h |
Participantsdifferent | 2-8 | 1-8 | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Concept Map, Relationship Labels, Knowledge Gaps | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | KnowledgeConceptsMappingSensemaking | QualityProblem solvingRoot cause | KnowledgeDomain-Driven DesignProcess |