View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Responsibility Poker |  Systems Thinking Iceberg Model |  Operations MORT Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | 45-90 min | 30-60 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-10 | 2-10 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Iceberg Worksheet, Pattern Notes, Intervention Ideas | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Systems thinkingRoot causePatterns | Root causeSafetySystemicIncident | Root causeSafetyIncident |