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 Visual Management |  Operations Bottleneck Analysis |  Architecture C4 Model |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | Ongoing | 1-3 h | 1-4 h | Ongoing |
Participantsdifferent | 1-20 | 3-8 | 1-5 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Diagram, Container Diagram, Component Diagram | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | SignalsOperationsVisual management | FlowMeasurementConstraints | ArchitectureCommunicationVisualization | FlowVisual managementDelivery |