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 Funnel Analysis |  Agile 4Ls Retrospective |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45–75 min | 30-60 min | 45-90 min |
Participantsdifferent | 1-5 | Team members involved | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AnalyticsConversionGrowth | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |