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 |  Product Strategy Lean Canvas |  Business Strategy Value Chain Analysis |  Delivery Value Stream Mapping |
|---|---|---|---|---|
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 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | Ongoing | 45-90 min | Half day | 1-3 h |
Participantsdifferent | 2-12 | 1-6 | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Lean Canvas, Core Assumptions, Experiment Backlog | Value Chain Map, Lever List | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | StartupLeanAssumptionsBusiness model | StrategyBusiness modelDiagnosisAnalysis | LeanFlowWasteDelivery |