View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Architecture Architecture Communication Canvas | ![]() Operations Bottleneck Analysis | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-120 min | 1-3 h | 1-4 h |
Participantsdifferent | 4-10 | 2-8 | 3-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureCommunicationStakeholdersCanvas | FlowMeasurementConstraints | ArchitectureCommunicationVisualization |



