View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Starfish Retrospective | ![]() Growth Funnel Analysis | ![]() Growth A/B Testing | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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 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 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 | Low | Medium | High | Low |
Timedifferent | 45-90 min | 1-3 h | 1-4 Wochen | 30-60 min |
Participantsdifferent | 4-12 | 1-5 | 1-6 | 3-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Funnel report, Drop-off analysis, Optimization hypotheses | Experiment results, Decision log, Learning summary | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | AnalyticsConversionGrowth | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementTeamReflection |



