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 MORT Analysis | ![]() Operations Family Tree Analysis | ![]() Decision Making Assumption Surfacing | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 2-4 h | 45-90 min | 45-60 min |
Participantsdifferent | 2-6 | 2-6 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |



