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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.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.For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.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.
Complexitydifferent
HighLowHighMedium
Timedifferent
2-6 h30 min Setup, dann laufend2-8 h1-4 h
Participantsdifferent
3-101-3 maintaining, briefing for everyone2-83-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsRAID Log, Status Report SourceProblem Analysis, Decision Analysis, Risk PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
RiskQualityOperationsRoot cause
RiskTrackingStakeholdersGovernance
Problem solvingRoot causeDecisionOperations
Root causeProblem solvingQualityIncident
Add more methods