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 Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
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 Current Reality Tree
Systems Thinking
Current Reality Tree
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
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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.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.
Complexitydifferent
MediumLowHighLow
Timedifferent
1-2 h30-60 min2-6 h45–75 min
Participantsdifferent
3-123-123-8Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsStart Stop Continue Board, Improvement ActionsCurrent Reality Tree, Core Problems, Intervention Ideas4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
Systems thinkingTradeoffsLeadership
RetrospectiveImprovementTeamReflection
Systems thinkingRoot causeConstraintsCausality
RetrospectiveLearningReflectionTeam
Add more methods