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 Causal Factor Analysis.
Operations
Causal Factor Analysis
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.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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
MediumHighHighLow
Timedifferent
1-3 h1-4 Wochen2-6 h1-5 Tage
Participantsdifferent
3-121-63-10Nutzertraffic
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
System Map, Dependencies, Leverage PointsExperiment results, Decision log, Learning summaryEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
Systems thinkingMappingBoundariesChange
ExperimentsGrowthAnalyticsValidation
CausalityIncidentRoot causeTimeline
ValidationExperimentsDemandGrowth
Add more methods