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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
MediumMediumHighLow
Timedifferent
2-6 h30-90 min1-4 Wochen1-5 Tage
Participantsdifferent
2-81-61-6Nutzertraffic
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDecision Tree, Option Map, Assumption ListExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
DecisionTreeOptions
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods