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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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 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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
20-40 min initial, dann laufend30 min Setup, dann laufend1-4 h1-3 h
Participantsdifferent
3-151-3 maintaining, briefing for everyone3-82-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListRAID Log, Status Report SourceProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Root causeProblem solvingQualityIncident
Root causeTreeIncidentQuality
Add more methods