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 Knowledge Mapping.
Knowledge Modeling
Knowledge 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
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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
1-3 h2-8 h60-180 min1-3 h
Participantsdifferent
3-125-124-201-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsCynefin Map, Domain-specific Actions, Sensemaking NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
KnowledgeMappingRisk
Domain-Driven DesignEventsDiscoveryWorkshop
ComplexitySensemakingDecision
SensemakingDecisionRationale
Add more methods