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
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 of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
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
Purposedifferent
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.The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible.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.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min25-40 min30-60 min45-90 min
Participantsdifferent
Team members involved1-53-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsLearning Card with evidence and next actionStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
RetrospectiveLearningReflectionTeam
ExperimentsValidationDiscoveryLearning
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods