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 Weekly Review.
Operations
Weekly Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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 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.
Complexitysame
LowLowLow
Timedifferent
30-60 min30-60 min45–75 min
Participantsdifferent
13-12Team members involved
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Updated Task System, Weekly Focus, Next ActionsStart Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ProductivityExecutionPlanning
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective