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 Bounded Context Canvas |  Operations Family Tree Analysis |  Domain Modeling Context Map |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 2-4 h | 1-3 h | 15-30 min |
Participantsdifferent | 3-8 | 2-6 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Family Tree Diagram, Pattern Notes, Systemic Measures | Context Map, Integration Patterns, Boundary Notes | Root cause notes, Countermeasures |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | Root causePatternsIncidentSystemic | Domain-Driven DesignBoundariesStrategy | Root causeIncidentLeanProblem solving |