View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Runbook | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Evaporating Cloud | ![]() Systems Thinking Systems Mapping |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 20-60 min | 2-4 h | 60-120 min | 1-3 h |
Participantsdifferent | 1-4 | 3-8 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | System Map, Dependencies, Leverage Points |
Tagsno overlap | OperationsReliabilityDocumentation | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingMappingBoundariesChange |



