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 Monte Carlo Forecasting |  Product Strategy Lean Canvas |  Business Strategy 5-Minuten VC-Check |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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 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 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 45-90 min | 5-15 min | Ongoing |
Participantsdifferent | 1-8 | 1-6 | 1-5 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Lean Canvas, Core Assumptions, Experiment Backlog | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingFlowDelivery | StartupLeanAssumptionsBusiness model | StartupValidationCompetition | FlowVisual managementDelivery |