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 Iceberg Model |  Facilitation Responsibility Poker |  Operations Family Tree Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 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 | Low | Low | Medium | High |
Timedifferent | 30-60 min | 45-90 min | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-10 | 3-10 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Responsibility Map, Role Agreements, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Systems thinkingRoot causePatterns | RolesResponsibilityTeamFacilitation | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |