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 Bottleneck Analysis |  Domain Modeling Context Map |  DevOps Incident Command |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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 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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | As needed | 2-4 h Analyse, laufend |
Participantsdifferent | 3-8 | 2-8 | 4-15 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Map, Integration Patterns, Boundary Notes | Incident Log, Action Tracker, Stakeholder Updates | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowMeasurementConstraints | Domain-Driven DesignBoundariesStrategy | IncidentOperationsReliability | OperationsConstraintsFlowImprovement |