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 C4 Model |  Architecture Architecture Decision Record |  Engineering Kanban |
|---|---|---|---|---|
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 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. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-4 h | 15-45 min | Ongoing |
Participantsdifferent | 4-10 | 1-5 | 1-3 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | FlowVisual managementDelivery |