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 Domain Context Map |  Domain Modeling Context Map |  Operations Waste Analysis |
|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 h | 45-120 min |
Participantsdifferent | 3-10 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Context Map, Integration Patterns, Boundary Notes | Waste Map, Prioritized Waste, Improvement Backlog |
Tagsno overlap | Domain-Driven DesignContextBoundaries | Domain-Driven DesignBoundariesStrategy | WasteLeanProcess improvement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
