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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Purposedifferent
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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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.
Complexitydifferent
HighHighHighMedium
Timedifferent
1-4 Wochen2-6 hMehrere Tage bis Wochen2-4 h
Participantsdifferent
1-63-82-62-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryFault Tree, Critical Paths, Cause Hypotheses, Control ActionsMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
RiskRoot causeSafety
Root causeSafetySystemicIncident
Root causePatternsIncidentSystemic
Add more methods