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
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
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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
MediumHighLowLow
Timedifferent
1-3 h1-4 Wochen5-20 min1-5 Tage
Participantsdifferent
3-121-63-20Nutzertraffic
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
System Map, Dependencies, Leverage PointsExperiment results, Decision log, Learning summaryEffort Heatmap, Risk Signals, Discussion TargetsInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
Systems thinkingMappingBoundariesChange
ExperimentsGrowthAnalyticsValidation
EstimationEffortRisk
ValidationExperimentsDemandGrowth
Add more methods