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 Shape-First Modeling |  Operations 5 Whys |  Operations Root Cause Analysis |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Halber Tag pro Domain Slice | 15-30 min | 1-4 h | 45-90 min |
Participantsdifferent | 1-4 | 2-6 | 3-8 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Knowledge graphValidationSemantic | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident | LeanProblem solvingCoachingOperations |