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 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 45-90 min | 30-60 min | 15-30 min | 1-6 Wochen |
Participantsdifferent | 3-10 | 2-10 | 2-6 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Systems thinkingRoot causePatterns | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |