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 | ![]() Operations Fault Tree Analysis | ![]() Decision Making Assumption Surfacing | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | 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 | Medium | High | Low | Medium |
Timedifferent | 2-4 h | 2-6 h | 45-90 min | 45-60 min |
Participantsdifferent | 2-6 | 3-8 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Root causePatternsIncidentSystemic | RiskRoot causeSafety | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |



