View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling EventStorming |  Decision Making Assumption Surfacing |  Knowledge Modeling Domain Storytelling |  Facilitation Decision Jam |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 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 | Medium | Low | Low | Low |
Timedifferent | 2-8 h | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 5-12 | 2-8 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Assumption List, Critical Assumptions, Learning Plan | Domain Story, Glossary Notes, Process Narrative | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | AssumptionsRiskDecisionDiscovery | KnowledgeDomain-Driven DesignProcess | FacilitationDecisionProblem solvingWorkshop |