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 4Ls Retrospective |  Systems Thinking Evaporating Cloud |  Operations Learning Review |
|---|---|---|---|---|
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 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 2-4 h | 45–75 min | 60-120 min | 1-3 h |
Participantsdifferent | 3-8 | Team members involved | 2-8 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | 4Ls Board, Learning Themes, Improvement Actions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | RetrospectiveLearningReflectionTeam | Theory of ConstraintsAssumptionsSystems thinking | LearningRetrospectiveIncidentOperations |