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 | ![]() Growth Funnel Analysis | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-120 min | 45-90 min | 1-3 h | 30-60 min |
Participantsdifferent | 3-8 | 4-12 | 1-5 | 3-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Starfish Board, Practice Changes, Experiments | Funnel report, Drop-off analysis, Optimization hypotheses | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | GrowthRetentionConversion | RetrospectiveImprovementExperimentsTeam | AnalyticsConversionGrowth | RetrospectiveImprovementTeamReflection |



