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 for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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 a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighMediumHighMedium
Timedifferent
2-6 h60-120 min1-4 Wochen2-4 h
Participantsdifferent
3-83-81-62-6
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Root causeSafetyIncident
Add more methods