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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
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.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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.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
HighHighMediumMedium
Timedifferent
2-6 h1-4 Wochen2-4 h2-4 h
Participantsdifferent
3-81-62-62-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsExperiment results, Decision log, Learning summaryFamily Tree Diagram, Pattern Notes, Systemic MeasuresBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
ExperimentsGrowthAnalyticsValidation
Root causePatternsIncidentSystemic
Root causeSafetyIncident
Add more methods