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 the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.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.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
MediumLowMediumMedium
Timedifferent
2-8 h60-90 min1-3 h1-3 h
Participantsdifferent
5-124-102-81-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsProblem Cluster, Prioritized Challenge, ExperimentIssue Map, Positions, Argument NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
FacilitationDecisionProblem solvingWorkshop
RationaleKnowledgeDecision
SensemakingDecisionRationale
Add more methods