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 |  Engineering Kanban |  Product Discovery Riskiest Assumption Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 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 idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 30-90 min Setup, danach laufend | Ongoing | 1-2 Wochen pro Iteration | 1-5 Tage |
Participantsdifferent | 1-8 | 2-12 | 2-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ForecastingFlowDelivery | FlowVisual managementDelivery | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery |