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 Start Stop Continue | ![]() Agile Starfish Retrospective | ![]() Agile 4Ls 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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 | High | Low | Low | Low |
Timedifferent | 0.5-3 Tage | 30-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 5-15 | 3-12 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |



