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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for ABC Analysis
Operations
ABC Analysis
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.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.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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 min30-120 min30-60 minAs needed
Participantsdifferent
1-42-61-54-15
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathObservation Notes, Improvement IdeasABC Classification, Focus Rules, Control ListIncident Log, Action Tracker, Stakeholder Updates
Tags1 shared
OperationsReliabilityDocumentation
LeanObservationProcessOperations
PrioritizationOperationsPortfolio
IncidentOperationsReliability
Add more methods