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 Leverage Points |  DevOps Game Day |  Systems Thinking Evaporating Cloud |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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 preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | High | High | Medium | Low |
Timedifferent | Half day | Halber Tag | 60-120 min | 45-90 min |
Participantsdifferent | 3-12 | 5-20 | 2-8 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Leverage Map, Action Strategy | Simulation Notes, Gaps List, Updated Runbooks | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Systems thinkingChangeStrategy | ResilienceOperationsIncident | Theory of ConstraintsAssumptionsSystems thinking | ChangeDecisionStrategy |