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/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Purposedifferent
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.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.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.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.
Complexitydifferent
HighMediumLowLow
Timedifferent
1-4 Wochen2-6 h1-5 Tage30-60 min
Participantsdifferent
1-62-8Nutzertraffic1-5
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryEvent Model, UI Flow, Commands, Read ModelsInterest Metrics, Conversion Signal, Learning NoteCompleted Experiment Canvas, Success Metric
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
EventsBlueprintDomain-Driven DesignBehavior
ValidationExperimentsDemandGrowth
ExperimentsValidationDiscoveryHypothesis
Add more methods