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 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 20-45 min | 60-120 min |
Participantsdifferent | 3-12 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Lessons learned, Action items, Event summary | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | Systems thinkingMappingBoundariesChange | LearningOperationsImprovement | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
