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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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
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.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.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
MediumLowMediumLow
Timedifferent
1-3 h30-60 min0.5-5 Tage45–75 min
Participantsdifferent
3-103-124-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogStart Stop Continue Board, Improvement ActionsKaizen Charter, Waste List, Improvement Experiments, Standard Work Update4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ProcessOperationsImprovement
RetrospectiveImprovementTeamReflection
LeanContinuous improvementOperations
RetrospectiveLearningReflectionTeam
Add more methods