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 | ![]() Operations A3 Problem Solving | ![]() Operations Family Tree Analysis | ![]() Operations Learning Review |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-60 min | 45-90 min | 2-4 h | 1-3 h |
Participantsdifferent | 1 | 2-5 | 2-6 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | A3 Report, Action Plan, Root Cause Analysis | Family Tree Diagram, Pattern Notes, Systemic Measures | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | LearningKnowledgeUnderstanding | LeanProblem solvingCoachingOperations | Root causePatternsIncidentSystemic | LearningRetrospectiveIncidentOperations |



