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 arc42 |  Operations Theory of Constraints |  Operations After-Action Review |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 1-2 Tage | 2-4 h Analyse, laufend | 20-45 min |
Participantsdifferent | 3-8 | 1-4 | 3-12 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Architecture Document, Context View, Runtime View, Deployment View | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureDocumentationCommunication | OperationsConstraintsFlowImprovement | LearningOperationsImprovement |