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 Game Day |  Systems Thinking Leverage Points |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 60-120 min | Halber Tag | Half day | 45-90 min |
Participantsdifferent | 2-8 | 5-20 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Simulation Notes, Gaps List, Updated Runbooks | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ResilienceOperationsIncident | Systems thinkingChangeStrategy | ChangeDecisionStrategy |