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
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 Root Cause Analysis.
Operations
Root Cause Analysis
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.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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowMedium
Timedifferent
30-60 min45–75 min1-4 h
Participantsdifferent
3-12Team members involved3-8
Formatdifferent
WorkshopWorkshopWorkshop + async
Outputdifferent
Start Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Root causeProblem solvingQualityIncident
Add more methods

Often compared together

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

Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Learning Review.
Operations
Learning Review