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 Systems Mapping |  Operations Family Tree Analysis |  Systems Thinking Iceberg Model |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 2-4 h | 30-60 min | 2-4 h |
Participantsdifferent | 3-12 | 2-6 | 2-10 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Family Tree Diagram, Pattern Notes, Systemic Measures | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Root causePatternsIncidentSystemic | Systems thinkingRoot causePatterns | Root causeSafetyIncident |