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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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 RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
LowMediumMedium
Timedifferent
20-60 min30-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-41-63-20 Reviewer
Formatdifferent
AsyncWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
ArchitectureDecisionAsyncGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 Constraint Analysis.
Decision Making
Constraint Analysis