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
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Process Mapping method illustration showing its working structure
Operations
Process Mapping
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
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.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 a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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
MediumMediumLowLow
Timedifferent
0.5-5 Tage1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-120 min
Participantsdifferent
4-103-10Scrum Team2-6
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Kaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateProcess Map, Handoff List, Improvement BacklogImprovement actions, Team agreementsObservation Notes, Improvement Ideas
Tagsno overlap
LeanContinuous improvementOperations
ProcessOperationsImprovement
RetrospectiveImprovementLearning
LeanObservationProcessOperations
Add more methods