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 Feynman Technique | ![]() Knowledge Modeling Knowledge Mapping | ![]() Operations Family Tree Analysis | ![]() Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 20-60 min | 1-3 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 1 | 3-12 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | LearningKnowledgeUnderstanding | KnowledgeMappingRisk | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |



