View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile 4Ls Retrospective | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Intervention Mapping | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Low | High | High | Medium |
Timedifferent | 45–75 min | 2-4 h | 1-5 Tage | 60-120 min |
Participantsdifferent | Team members involved | 3-8 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | RetrospectiveLearningReflectionTeam | Theory of ConstraintsSystems thinkingChange | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking |



