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 | ![]() Operations Causal Factor Analysis | ![]() Operations 5 Whys |
|---|---|---|---|---|
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. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 1-2 h | Mehrere Tage bis Wochen | 2-6 h | 15-30 min |
Participantsdifferent | 1-8 | 2-6 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Root cause notes, Countermeasures |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Root causeSafetySystemicIncident | CausalityIncidentRoot causeTimeline | Root causeIncidentLeanProblem solving |



