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
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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowMediumLowLow
Timedifferent
20-60 minAs needed15-45 min1-2 Tage
Participantsdifferent
1-44-151-31-4
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathIncident Log, Action Tracker, Stakeholder UpdatesADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
OperationsReliabilityDocumentation
IncidentOperationsReliability
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods