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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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.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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-120 min1-3 h30-60 min45–75 min
Participantsdifferent
2-63-103-12Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Observation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogStart Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LeanObservationProcessOperations
ProcessOperationsImprovement
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods