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 Evaporating Cloud |  DevOps Blameless Postmortem |  Agile 4Ls Retrospective |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 60-120 min | 30-90 min | 45–75 min | 2-4 h |
Participantsdifferent | 2-8 | 3-12 | Team members involved | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Postmortem Doc, Action Items, Timeline | 4Ls Board, Learning Themes, Improvement Actions | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveLearningReflectionTeam | Theory of ConstraintsSystems thinkingChange |