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 |  Engineering Kanban |  Architecture arc42 |
|---|---|---|---|---|
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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 1-4 h | Ongoing | 1-2 Tage |
Participantsdifferent | 3-8 | 1-5 | 2-12 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Diagram, Container Diagram, Component Diagram | Kanban board, WIP policies, Flow metrics | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureCommunicationVisualization | FlowVisual managementDelivery | ArchitectureDocumentationCommunication |