View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery Value Stream Mapping |  Architecture Architecture Communication Canvas |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Ongoing | 1-3 h | 60-120 min | 1-2 h |
Participantsdifferent | 2-12 | 4-10 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | ArchitectureCommunicationStakeholdersCanvas | AlignmentArchitectureCanvas |