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 |  Agile Starfish Retrospective |  Agile Start Stop Continue |  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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | 45-90 min | 30-60 min | 1-4 Wochen |
Participantsdifferent | 3-8 | 4-12 | 3-12 | 1-6 |
Formatdifferent | Workshop | Workshop | Workshop | Async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Experiment results, Decision log, Learning summary |
Tagsno overlap | GrowthRetentionConversion | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | ExperimentsGrowthAnalyticsValidation |