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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
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.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.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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
MediumLowHighLow
Timedifferent
1-3 h20-45 min2-6 h30-120 min
Participantsdifferent
3-103-123-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogLessons learned, Action items, Event summaryFault Tree, Critical Paths, Cause Hypotheses, Control ActionsObservation Notes, Improvement Ideas
Tagsno overlap
ProcessOperationsImprovement
LearningOperationsImprovement
RiskRoot causeSafety
LeanObservationProcessOperations
Add more methods