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 4Ls Retrospective | ![]() Agile Start Stop Continue | ![]() 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 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. | 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 | Low |
Timedifferent | 0.5-3 Tage | 45–75 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 5-15 | Team members involved | 3-12 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning |



