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 |  Operations Bottleneck Analysis |  Operations After-Action Review |  Domain Modeling Context Map |
|---|---|---|---|---|
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. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 20-45 min | 1-3 h |
Participantsdifferent | 3-10 | 3-8 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Lessons learned, Action items, Event summary | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | FlowMeasurementConstraints | LearningOperationsImprovement | Domain-Driven DesignBoundariesStrategy |