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 |  Growth A/B Testing |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 60-120 min | 1-4 Wochen | 45-60 min |
Participantsdifferent | 4-10 | 3-8 | 1-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanFlowWasteDelivery | GrowthRetentionConversion | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation |