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 Dot Estimation.
Facilitation
Dot Estimation
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.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 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 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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
5-20 min1-3 h1-5 Tage1-4 Wochen
Participantsdifferent
3-203-12Nutzertraffic1-6
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsSystem Map, Dependencies, Leverage PointsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
EstimationEffortRisk
Systems thinkingMappingBoundariesChange
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods