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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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
MediumMediumLowMedium
Timedifferent
2-8 h1-3 h1-2 h1-3 h
Participantsdifferent
5-122-82-81-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsIssue Map, Positions, Argument NotesDIBB document, Belief list, Bet list, Learning reportArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RationaleKnowledgeDecision
StrategyDecisionAssumptionsHypothesis
SensemakingDecisionRationale
Add more methods