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
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
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 Mad Sad Glad
Agile
Mad Sad Glad
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 PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min1-3 h Setup, laufend30-60 min30-60 min
Participantsdifferent
Team members involved13-123-10
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsPARA Structure, Project Notes, Knowledge ArchiveStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
KnowledgeProductivityOrganization
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods