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
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
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
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.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
LowMediumLowLow
Timedifferent
30-120 minAs needed1-2 Tage20-60 min
Participantsdifferent
2-64-151-41-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Observation Notes, Improvement IdeasIncident Log, Action Tracker, Stakeholder UpdatesArchitecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation Path
Tagsno overlap
LeanObservationProcessOperations
IncidentOperationsReliability
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
Add more methods