View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Soft Systems Methodology | ![]() Agile Sailboat Retrospective | ![]() Agile Sprint Retrospective |
|---|---|---|---|
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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | High | Low | Low |
Timedifferent | 0.5-3 Tage | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 5-15 | 4-12 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






