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 | ![]() Decision Making Assumption Surfacing | ![]() Knowledge Modeling Event Modeling | ![]() Knowledge Modeling IBIS |
|---|---|---|---|---|
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. | 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. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 h | 45-90 min | 2-6 h | 1-3 h |
Participantssame | 2-8 | 2-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Assumption List, Critical Assumptions, Learning Plan | Event Model, UI Flow, Commands, Read Models | Issue Map, Positions, Argument Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | AssumptionsRiskDecisionDiscovery | EventsBlueprintDomain-Driven DesignBehavior | RationaleKnowledgeDecision |



