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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20-60 min1-3 h45-90 min15-45 min
Participantsdifferent
1-41-82-81-3
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathArgument Map, Evidence Gaps, Decision RationaleRACI Matrix, Responsibility Map, Decision NotesADR File, Decision Log, Rationale
Tagsno overlap
OperationsReliabilityDocumentation
SensemakingDecisionRationale
RolesResponsibilityGovernanceOperations
ArchitectureRationaleDocumentationGovernance
Add more methods