View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Systems Thinking Iceberg Model |  Decision Making Force Field Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-90 min | 30-60 min | 45-90 min | 15-30 min |
Participantsdifferent | 3-12 | 2-10 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Force Field Map, Change Levers, Risk Notes | Root cause notes, Countermeasures |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | Systems thinkingRoot causePatterns | ChangeDecisionStrategy | Root causeIncidentLeanProblem solving |