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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30-120 minOngoing30-60 min1-4 h
Participantsdifferent
2-62-202-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Observation Notes, Improvement IdeasChat Transcript, Action Log, AutomationsFishbone Diagram, Cause Categories, Investigation BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
LeanObservationProcessOperations
CollaborationEngineeringIncident
Root causeQualityOperations
Root causeProblem solvingQualityIncident
Add more methods