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
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Purposedifferent
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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.
Complexitydifferent
LowMediumHighMedium
Timedifferent
1-5 Tage1-3 h1-4 Wochen1-3 h
Participantsdifferent
Nutzertraffic3-121-61-5
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
Interest Metrics, Conversion Signal, Learning NoteSystem Map, Dependencies, Leverage PointsExperiment results, Decision log, Learning summaryFunnel report, Drop-off analysis, Optimization hypotheses
Tagsno overlap
ValidationExperimentsDemandGrowth
Systems thinkingMappingBoundariesChange
ExperimentsGrowthAnalyticsValidation
AnalyticsConversionGrowth
Add more methods