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 Future Reality Tree | ![]() Agile Start Stop Continue | ![]() Agile 4Ls Retrospective |
|---|---|---|---|
Purposedifferent | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 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 |
Timedifferent | 2-4 h | 30-60 min | 45–75 min |
Participantsdifferent | 3-8 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






