View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Family Tree Analysis |  Growth A/B Testing |  Product Discovery Assumption Mapping |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 2-4 h | 1-4 Wochen | 45-60 min | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 1-6 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causePatternsIncidentSystemic | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation | Root causeSafetySystemicIncident |