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 Failure Mode and Effects Analysis |  Operations Fishbone Diagram |
|---|---|---|---|---|
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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 45-120 min | 2-6 h | 30-60 min |
Participantsdifferent | 2-8 | 2-6 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeRoot causeTroubleshootingComparison | RiskQualityOperationsRoot cause | Root causeQualityOperations |