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
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Fake Door Test
Product Discovery
Fake Door 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 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 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
MediumLowHighMedium
Timedifferent
1-3 h5-20 min1-4 Wochen1-5 Tage
Participantsdifferent
3-123-201-6Nutzertraffic
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
System Map, Dependencies, Leverage PointsEffort Heatmap, Risk Signals, Discussion TargetsExperiment results, Decision log, Learning summaryClick Data, Interest Signal, Learning Decision
Tagsno overlap
Systems thinkingMappingBoundariesChange
EstimationEffortRisk
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandDiscovery
Add more methods