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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h45–75 min30-60 min
Participantsdifferent
2-8Team members involved3-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Cause Tree, Evidence Notes, Countermeasures4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
Root causeTreeIncidentQuality
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

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

Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective