View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Operations MORT Analysis |  Knowledge Modeling IBIS |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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 | Medium | High | Medium | Medium |
Timedifferent | 1-2 h | Mehrere Tage bis Wochen | 1-3 h | 2-4 h |
Participantsdifferent | 1-8 | 2-6 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Issue Map, Positions, Argument Notes | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Root causeSafetySystemicIncident | RationaleKnowledgeDecision | Root causePatternsIncidentSystemic |