View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Knowledge Modeling Competency Questions |  Operations 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 30 min Setup, dann laufend | 2-4 h | 15-30 min | 1-6 Wochen |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 2-6 | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OntologyKnowledge graphScopeRequirementsSemantic | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |