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 |  Domain Modeling Context Map |  Operations Bottleneck Analysis |  Product Strategy Counter Metrics |
|---|---|---|---|---|
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. | 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 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. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 1-3 h | 30-60 min |
Participantsdifferent | 3-12 | 2-8 | 3-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Context Map, Integration Patterns, Boundary Notes | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Counter Metric List, Guardrail Definitions |
Tagsno overlap | OperationsConstraintsFlowImprovement | Domain-Driven DesignBoundariesStrategy | FlowMeasurementConstraints | MetricsMeasurementStrategyExperiments |