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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
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.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.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 Tage20-60 min15-45 minAs needed
Participantsdifferent
1-41-41-34-15
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation PathADR File, Decision Log, RationaleIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
ArchitectureRationaleDocumentationGovernance
IncidentOperationsReliability
Add more methods