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 5 Whys |  Decision Making Force Field Analysis |  Operations 8D 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 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. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 h | 15-30 min | 45-90 min | 1-6 Wochen |
Participantsdifferent | 2-8 | 2-6 | 3-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Root cause notes, Countermeasures | Force Field Map, Change Levers, Risk Notes | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Root causeIncidentLeanProblem solving | ChangeDecisionStrategy | QualityProblem solvingRoot cause |