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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-60 min1-2 h Setup, laufend45–75 min45-90 min
Participantsdifferent
3-121Team members involved4-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsAction Lists, Project List, Review Routine4Ls Board, Learning Themes, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
RetrospectiveImprovementTeamReflection
ProductivityPlanningTasksExecution
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementExperimentsTeam
Add more methods