View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Lean Startup |  Product Discovery Pretotyping |  Engineering Kanban |  Product Strategy Lean Canvas |
|---|---|---|---|---|
Purposedifferent | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage | Ongoing | 45-90 min |
Participantsdifferent | 2-8 | 1-4 | 2-12 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Kanban board, WIP policies, Flow metrics | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | LeanStartupValidationMVP | ValidationDemandMVP | FlowVisual managementDelivery | StartupLeanAssumptionsBusiness model |