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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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
Purposedifferent
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
As needed45-90 min1-2 Tage20-60 min
Participantsdifferent
4-152-51-41-4
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesA3 Report, Action Plan, Root Cause AnalysisArchitecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation Path
Tagsno overlap
IncidentOperationsReliability
LeanProblem solvingCoachingOperations
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
Add more methods