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 |  Business Strategy 5-Minuten VC-Check |  Product Strategy Lean Canvas |  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. | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | 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. | 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 | Low | Medium | Medium |
Timedifferent | Ongoing | 5-15 min | 45-90 min | 1-3 h |
Participantsdifferent | 2-12 | 1-5 | 1-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Lean Canvas, Core Assumptions, Experiment Backlog | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | StartupValidationCompetition | StartupLeanAssumptionsBusiness model | LeanFlowWasteDelivery |