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