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 |  Business Strategy GAP Analysis |  Operations Root Cause Analysis |  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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 1-4 h | 2-4 h |
Participantsdifferent | 2-8 | 2-8 | 3-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Gap Matrix, Action Plan, Risk Notes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyAnalysisPlanning | Root causeProblem solvingQualityIncident | Root causeSafetyIncident |