View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Context Map | ![]() Systems Thinking Iceberg Model | ![]() Operations Causal Factor Analysis | ![]() Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 30-60 min | 2-6 h | 2-4 h |
Participantsdifferent | 2-8 | 2-10 | 3-10 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Systems thinkingRoot causePatterns | CausalityIncidentRoot causeTimeline | Root causePatternsIncidentSystemic |



