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 MORT 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h | Ongoing | 30-60 min | Mehrere Tage bis Wochen |
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 | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causePatternsIncidentSystemic | CollaborationEngineeringIncident | Systems thinkingRoot causePatterns | Root causeSafetySystemicIncident |