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 Intervention Mapping |  DevOps Blameless Postmortem |  Decision Making Assumption Surfacing |  Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 1-5 Tage | 30-90 min | 45-90 min | 60-120 min |
Participantsdifferent | 4-12 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | ChangeSystems thinkingCapability | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery | Theory of ConstraintsAssumptionsSystems thinking |