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 Systems Mapping | ![]() Operations After-Action Review | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 20-45 min | 2-4 h | 60-120 min |
Participantsdifferent | 3-12 | 3-12 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Lessons learned, Action items, Event summary | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | Systems thinkingMappingBoundariesChange | LearningOperationsImprovement | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking |



