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 |  Architecture C4 Model |  Operations Theory of Constraints |  Operations Process Mapping |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 1-4 h | 2-4 h Analyse, laufend | 1-3 h |
Participantsdifferent | 3-8 | 1-5 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Diagram, Container Diagram, Component Diagram | Constraint Map, Improvement Plan, Flow Metrics | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureCommunicationVisualization | OperationsConstraintsFlowImprovement | ProcessOperationsImprovement |