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 Kepner-Tregoe |  Decision Making Force Field Analysis |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 2-8 h | 45-90 min | 45-90 min |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 2-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Problem Analysis, Decision Analysis, Risk Plan | Force Field Map, Change Levers, Risk Notes | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Problem solvingRoot causeDecisionOperations | ChangeDecisionStrategy | LeanProblem solvingCoachingOperations |