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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
2-6 h1-3 h1-4 Wochen1-3 h
Participantsdifferent
2-82-81-61-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsIssue Map, Positions, Argument NotesExperiment results, Decision log, Learning summaryArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
RationaleKnowledgeDecision
ExperimentsGrowthAnalyticsValidation
SensemakingDecisionRationale
Add more methods