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 Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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 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.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-8 h60-180 min1-2 h1-3 h
Participantsdifferent
5-124-201-81-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsCynefin Map, Domain-specific Actions, Sensemaking NotesConcept Map, Relationship Labels, Knowledge GapsArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ComplexitySensemakingDecision
KnowledgeConceptsMappingSensemaking
SensemakingDecisionRationale
Add more methods