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
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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h30-120 minAs needed20-45 min
Participantsdifferent
3-102-64-153-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Process Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasIncident Log, Action Tracker, Stakeholder UpdatesLessons learned, Action items, Event summary
Tags1 shared
ProcessOperationsImprovement
LeanObservationProcessOperations
IncidentOperationsReliability
LearningOperationsImprovement
Add more methods