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 Fishbone Diagram | ![]() Operations Fault Tree Analysis |
|---|---|---|---|---|
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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 30 min Setup, dann laufend | 2-4 h | 30-60 min | 2-6 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 2-8 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OntologyKnowledge graphScopeRequirementsSemantic | Root causeQualityOperations | RiskRoot causeSafety |



