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 |  Facilitation Problem Framing Workshop |  Domain Modeling EventStorming |  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. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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 | Low | Medium | Low |
Timedifferent | 1-2 h | 60-120 min | 2-8 h | 60-90 min |
Participantsdifferent | 2-8 | 4-10 | 5-12 | 4-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | FacilitationAlignmentDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationDecisionProblem solvingWorkshop |