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 for Learning Review.
Operations
Learning Review
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min1-3 h20-45 min30-60 min
Participantsdifferent
Team members involved3-101-83-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsOwnership Reflection, Action Commitment, Coaching NotesStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
LearningRetrospectiveIncidentOperations
ResponsibilityLeadershipTeam
RetrospectiveImprovementTeamReflection
Add more methods