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 Blameless Postmortem |  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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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 | Medium | Low |
Timedifferent | 60-120 min | 30-90 min | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
