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 Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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 Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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'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
HighLowLowLow
Timedifferent
0.5-3 Tage45-90 min45–75 min30-60 min
Participantsdifferent
5-154-12Team members involved3-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaSailboat Board, Risks, Improvement Actions4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
RetrospectiveTeamImprovement
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods