View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Theory of Constraints |  Operations After-Action Review |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 2-4 h Analyse, laufend | 20-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 3-12 | 3-12 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries |