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 Waste Analysis |  Architecture C4 Model |  Delivery Value Stream Mapping |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. | 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 | Low | Medium | Low |
Timedifferent | 45-120 min | 1-4 h | 1-3 h | 1-2 Tage |
Participantsdifferent | 2-8 | 1-5 | 4-10 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Context Diagram, Container Diagram, Component Diagram | Current-state map, Future-state map, Bottleneck list | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | WasteLeanProcess improvement | ArchitectureCommunicationVisualization | LeanFlowWasteDelivery | ArchitectureDocumentationCommunication |