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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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 Argument Mapping
Decision Making
Argument Mapping
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
LowMediumLowMedium
Timedifferent
20-60 min30-90 min15-45 min1-3 h
Participantsdifferent
1-41-61-31-8
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods