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 |  Product Strategy Lean Canvas |  Architecture Architecture Communication Canvas |  Architecture arc42 |
|---|---|---|---|---|
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. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 60-120 min | 1-2 Tage |
Participantsdifferent | 4-10 | 1-6 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Lean Canvas, Core Assumptions, Experiment Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | LeanFlowWasteDelivery | StartupLeanAssumptionsBusiness model | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |