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 Change Analysis.
Operations
Change Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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
MediumLowMediumMedium
Timedifferent
45-120 min30 min Setup, dann laufend1-3 h1-4 h
Participantsdifferent
2-61-3 maintaining, briefing for everyone2-83-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListRAID Log, Status Report SourceCause Tree, Evidence Notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ChangeRoot causeTroubleshootingComparison
RiskTrackingStakeholdersGovernance
Root causeTreeIncidentQuality
Root causeProblem solvingQualityIncident
Add more methods