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 Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.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
HighMediumLowHigh
Timedifferent
2-6 hMultiple workshops over several weeks30-60 min1-4 Wochen
Participantsdifferent
3-82-81-51-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsHooked loop, Trigger map, Reward design, Ethics checkCompleted Experiment Canvas, Success MetricExperiment results, Decision log, Learning summary
Tagsno overlap
RiskRoot causeSafety
GrowthBehaviorRetention
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods