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 |  Decision Making Force Field Analysis |  Operations Root Cause 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 45-90 min | 1-4 h |
Participantsdifferent | 2-8 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
