View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fault Tree Analysis |  Delivery RAID Log |  Systems Thinking CATWOE Analysis |  Systems Thinking Iceberg Model |
|---|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. | 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. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 2-6 h | 30 min Setup, dann laufend | 45-90 min | 30-60 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 3-8 | 2-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | RAID Log, Status Report Source | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Iceberg Worksheet, Pattern Notes, Intervention Ideas |
Tagsno overlap | RiskRoot causeSafety | RiskTrackingStakeholdersGovernance | Systems thinkingFramingStakeholders | Systems thinkingRoot causePatterns |