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 Value Stream Mapping | ![]() Growth Flywheel | ![]() Product Discovery Smoke Test | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-120 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 4-10 | 3-8 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop | Workshop | Async | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | LeanFlowWasteDelivery | GrowthRetentionConversion | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |



