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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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
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
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufend2-4 h30-60 min2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone2-82-83-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixFishbone Diagram, Cause Categories, Investigation BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
OntologyKnowledge graphScopeRequirementsSemantic
Root causeQualityOperations
RiskRoot causeSafety
Add more methods