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 Software Architecture Canvas |  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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Low | Low |
Timedifferent | 1-3 h | 1-2 h | 1-4 h |
Participantsdifferent | 4-10 | 3-10 | 1-5 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Architecture Canvas, Goals, Constraints, Quality Attributes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | LeanFlowWasteDelivery | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
