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 Theory of Constraints |  Operations Bottleneck Analysis |  Operations After-Action Review |
|---|---|---|---|---|
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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | 2-4 h Analyse, laufend | 1-3 h | 20-45 min |
Participantsdifferent | 3-10 | 3-12 | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Lessons learned, Action items, Event summary |
Tagsno overlap | Domain-Driven DesignContextBoundaries | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints | LearningOperationsImprovement |