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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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 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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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
2-8 h1-3 h1-2 h60-90 min
Participantsdifferent
5-121-81-84-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsArgument Map, Evidence Gaps, Decision RationaleConcept Map, Relationship Labels, Knowledge GapsProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
SensemakingDecisionRationale
KnowledgeConceptsMappingSensemaking
FacilitationDecisionProblem solvingWorkshop
Add more methods