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
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
30-120 minAs needed0.5-5 TageHalber Tag
Participantsdifferent
2-64-154-105-20
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Observation Notes, Improvement IdeasIncident Log, Action Tracker, Stakeholder UpdatesKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateSimulation Notes, Gaps List, Updated Runbooks
Tags1 shared
LeanObservationProcessOperations
IncidentOperationsReliability
LeanContinuous improvementOperations
ResilienceOperationsIncident
Add more methods