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 of Hooked Model with its method-specific working model.
Growth
Hooked Model
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.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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
MediumMediumLowHigh
Timedifferent
1-3 hMultiple workshops over several weeks1-5 Tage1-4 Wochen
Participantsdifferent
3-122-8Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
System Map, Dependencies, Leverage PointsHooked loop, Trigger map, Reward design, Ethics checkInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
Systems thinkingMappingBoundariesChange
GrowthBehaviorRetention
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods