methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h2-6 h1-3 h1-3 h
Participantsdifferent
2-82-82-81-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Model, UI Flow, Commands, Read ModelsIssue Map, Positions, Argument NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
EventsBlueprintDomain-Driven DesignBehavior
RationaleKnowledgeDecision
SensemakingDecisionRationale
Add more methods