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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
LowLowMediumLow
Timedifferent
20-60 min15-45 min1-4 h30-60 min
Participantsdifferent
1-41-33-82-8
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathADR File, Decision Log, RationaleProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
OperationsReliabilityDocumentation
ArchitectureRationaleDocumentationGovernance
Root causeProblem solvingQualityIncident
Root causeQualityOperations
Add more methods