View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Flywheel |  Delivery RAID Log |  Product Discovery Experiment Canvas |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 60-120 min | 30 min Setup, dann laufend | 30-60 min | 1-4 Wochen |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 1-5 | 1-6 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | RAID Log, Status Report Source | Completed Experiment Canvas, Success Metric | Experiment results, Decision log, Learning summary |
Tagsno overlap | GrowthRetentionConversion | RiskTrackingStakeholdersGovernance | ExperimentsValidationDiscoveryHypothesis | ExperimentsGrowthAnalyticsValidation |