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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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
HighMediumHighLow
Timedifferent
1-4 Wochen1-3 hHalf day1-5 Tage
Participantsdifferent
1-62-83-12Nutzertraffic
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
Experiment results, Decision log, Learning summaryContext Map, Integration Patterns, Boundary NotesLeverage Map, Action StrategyInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
Domain-Driven DesignBoundariesStrategy
Systems thinkingChangeStrategy
ValidationExperimentsDemandGrowth
Add more methods