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 an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
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.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.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
LowLowMediumLow
Timedifferent
20-60 min45-90 minAs needed15-45 min
Participantsdifferent
1-42-84-151-3
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathRACI Matrix, Responsibility Map, Decision NotesIncident Log, Action Tracker, Stakeholder UpdatesADR File, Decision Log, Rationale
Tagsno overlap
OperationsReliabilityDocumentation
RolesResponsibilityGovernanceOperations
IncidentOperationsReliability
ArchitectureRationaleDocumentationGovernance
Add more methods