methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
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.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.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
MediumLowLowHigh
Timedifferent
2-4 h30 min Setup, dann laufend30-60 min2-6 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone2-83-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixRAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
RiskRoot causeSafety
Add more methods