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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Root Cause Analysis.
Operations
Root Cause 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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
LowHighMediumMedium
Timedifferent
30 min Setup, dann laufend2-6 h1-3 h1-4 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-103-103-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation ActionsLearning Review Notes, System Factors, Improvement ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
LearningRetrospectiveIncidentOperations
Root causeProblem solvingQualityIncident
Add more methods