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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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
20-60 min15-45 min30-120 minAs needed
Participantsdifferent
1-41-32-64-15
Formatdifferent
AsyncAsyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathADR File, Decision Log, RationaleObservation Notes, Improvement IdeasIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
ArchitectureRationaleDocumentationGovernance
LeanObservationProcessOperations
IncidentOperationsReliability
Add more methods