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
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 Starfish Retrospective
Agile
Starfish Retrospective
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
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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
MediumLowLowLow
Timedifferent
0.5-5 Tage30-60 min45-90 min45–75 min
Participantsdifferent
4-103-124-12Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Kaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LeanContinuous improvementOperations
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveLearningReflectionTeam
Add more methods