View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Domain Modeling Bounded Context Canvas |  Operations 5 Whys |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 h | 15-30 min | 1-3 h |
Participantsdifferent | 3-12 | 3-8 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Context Canvas, Glossary, Integration Notes | Root cause notes, Countermeasures | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | ChangeDecisionStrategy | Domain-Driven DesignBoundariesModeling | Root causeIncidentLeanProblem solving | Domain-Driven DesignBoundariesStrategy |