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 |  Operations A3 Problem Solving |  Operations Family Tree Analysis |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 45-90 min | 2-4 h | 2-8 h |
Participantsdifferent | 2-8 | 2-5 | 2-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | A3 Report, Action Plan, Root Cause Analysis | Family Tree Diagram, Pattern Notes, Systemic Measures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | LeanProblem solvingCoachingOperations | Root causePatternsIncidentSystemic | Problem solvingRoot causeDecisionOperations |