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 Waste 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. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 | Low | Medium |
Timedifferent | 1-3 h | 45-120 min | 2-4 h |
Participantsdifferent | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Waste Map, Prioritized Waste, Improvement Backlog | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | WasteLeanProcess improvement | Root causeSafetyIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
