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 |  Operations Barrier Analysis |  Systems Thinking Iceberg Model |  Operations Family Tree Analysis |
|---|---|---|---|---|
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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 2-4 h | 30-60 min | 2-4 h |
Participantsdifferent | 3-12 | 2-6 | 2-10 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | Root causeSafetyIncident | Systems thinkingRoot causePatterns | Root causePatternsIncidentSystemic |