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 illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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 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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
2-4 h30 min Setup, dann laufend1-4 h2-6 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-83-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixRAID Log, Status Report SourceProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
RiskTrackingStakeholdersGovernance
Root causeProblem solvingQualityIncident
RiskQualityOperationsRoot cause
Add more methods