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 Current Reality Tree
Systems Thinking
Current Reality Tree
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
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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.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
MediumHighLowHigh
Timedifferent
1-3 h2-6 h1-5 Tage1-4 Wochen
Participantsdifferent
3-123-8Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
System Map, Dependencies, Leverage PointsCurrent Reality Tree, Core Problems, Intervention IdeasInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
Systems thinkingMappingBoundariesChange
Systems thinkingRoot causeConstraintsCausality
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods