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 a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
20-60 min20-45 min1-3 h30-120 min
Participantsdifferent
1-43-123-102-6
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathLessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement Ideas
Tags1 shared
OperationsReliabilityDocumentation
LearningOperationsImprovement
ProcessOperationsImprovement
LeanObservationProcessOperations
Add more methods