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 Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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
LowMediumMediumLow
Timedifferent
20-60 min90-180 minAs needed15-45 min
Participantsdifferent
1-44-124-151-3
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathDecision Rights Matrix, AgreementIncident Log, Action Tracker, Stakeholder UpdatesADR File, Decision Log, Rationale
Tagsno overlap
OperationsReliabilityDocumentation
DecisionGovernanceAlignmentResponsibility
IncidentOperationsReliability
ArchitectureRationaleDocumentationGovernance
Add more methods