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 |  Delivery Monte Carlo Forecasting |  Architecture C4 Model |  Delivery Communication Plan |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-3 h | 30-90 min Setup, danach laufend | 1-4 h | 45-90 min |
Participantsdifferent | 4-10 | 1-8 | 1-5 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication | Context Diagram, Container Diagram, Component Diagram | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | LeanFlowWasteDelivery | ForecastingFlowDelivery | ArchitectureCommunicationVisualization | CommunicationStakeholdersDeliveryPlanning |