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 Current Reality Tree
Systems Thinking
Current Reality Tree
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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
LowHighHighLow
Timedifferent
45–75 min2-6 h2-6 h30-60 min
Participantsdifferent
Team members involved3-83-103-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsCurrent Reality Tree, Core Problems, Intervention IdeasEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
Systems thinkingRoot causeConstraintsCausality
CausalityIncidentRoot causeTimeline
RetrospectiveImprovementTeamReflection
Add more methods