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 A3 Problem Solving |  Knowledge Modeling Ontology Design Patterns |  Operations 5 Whys |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 h pro Pattern | 15-30 min | 2-4 h |
Participantsdifferent | 2-5 | 1-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Root cause notes, Countermeasures | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | LeanProblem solvingCoachingOperations | OntologyPatternsReuseSemanticModeling | Root causeIncidentLeanProblem solving | Root causePatternsIncidentSystemic |