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 Change Analysis |  Operations 5 Whys |  Operations Barrier 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 45-120 min | 15-30 min | 2-4 h |
Participantsdifferent | 2-8 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeRoot causeTroubleshootingComparison | Root causeIncidentLeanProblem solving | Root causeSafetyIncident |