View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Delivery Value Stream Mapping |  Delivery Communication Plan |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 1-3 h | 45-90 min | 1-2 Tage |
Participantsdifferent | 1-5 | 4-10 | 2-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Current-state map, Future-state map, Bottleneck list | Communication Plan, Channel Matrix, Message Cadence | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | LeanFlowWasteDelivery | CommunicationStakeholdersDeliveryPlanning | ArchitectureDocumentationCommunication |