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 Event Modeling |  Operations Kepner-Tregoe |  Facilitation Decision Jam |
|---|---|---|---|---|
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. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 h | 2-6 h | 2-8 h | 60-90 min |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Event Model, UI Flow, Commands, Read Models | Problem Analysis, Decision Analysis, Risk Plan | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | EventsBlueprintDomain-Driven DesignBehavior | Problem solvingRoot causeDecisionOperations | FacilitationDecisionProblem solvingWorkshop |