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 |  Delivery RAID Log |  Operations Failure Mode and Effects Analysis |  Systems Thinking CATWOE 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | 2-6 h | 45-90 min |
Participantsdifferent | 2-10 | 1-3 maintaining, briefing for everyone | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Iceberg Worksheet, Pattern Notes, Intervention Ideas | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingRoot causePatterns | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause | Systems thinkingFramingStakeholders |