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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
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.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.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-8 h1-3 h1-3 h60-180 min
Participantsdifferent
5-122-81-84-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsIssue Map, Positions, Argument NotesArgument Map, Evidence Gaps, Decision RationaleCynefin Map, Domain-specific Actions, Sensemaking Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RationaleKnowledgeDecision
SensemakingDecisionRationale
ComplexitySensemakingDecision
Add more methods