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 Root Cause Analysis |  Decision Making Force Field 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | High |
Timedifferent | 1-3 h | 1-4 h | 45-90 min | 2-8 h |
Participantsdifferent | 2-8 | 3-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Force Field Map, Change Levers, Risk Notes | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Root causeProblem solvingQualityIncident | ChangeDecisionStrategy | Problem solvingRoot causeDecisionOperations |