View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Family Tree Analysis |  DevOps ChatOps |  Systems Thinking Iceberg Model |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | Ongoing | 30-60 min | 2-4 h |
Participantsdifferent | 2-6 | 2-20 | 2-10 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Chat Transcript, Action Log, Automations | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causePatternsIncidentSystemic | CollaborationEngineeringIncident | Systems thinkingRoot causePatterns | Root causeSafetyIncident |