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 |  UX Design Storyboarding |  Architecture Architecture Decision Record |  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 a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Low | High |
Timedifferent | 1-3 h | 30-90 min | 15-45 min | 2-4 h Analyse, laufend |
Participantsdifferent | 3-8 | 1-8 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Storyboard, Concept Narrative, Testable Assumptions | ADR File, Decision Log, Rationale | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowMeasurementConstraints | VisualizationConceptsSequencePrototype | ArchitectureRationaleDocumentationGovernance | OperationsConstraintsFlowImprovement |