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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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 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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-6 h1-3 h1-3 h1-3 h
Participantsdifferent
2-83-121-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsKnowledge Map, Critical Knowledge Areas, Transfer PlanArgument Map, Evidence Gaps, Decision RationaleIssue Map, Positions, Argument Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
KnowledgeMappingRisk
SensemakingDecisionRationale
RationaleKnowledgeDecision
Add more methods