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
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Purposedifferent
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 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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h2-8 h30-90 min60-90 min
Participantsdifferent
1-85-121-64-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsDecision Tree, Option Map, Assumption ListProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
SensemakingDecisionRationale
Domain-Driven DesignEventsDiscoveryWorkshop
DecisionTreeOptions
FacilitationDecisionProblem solvingWorkshop
Add more methods