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 Sailboat Retrospective | ![]() Agile Start Stop Continue | ![]() Growth A/B Testing |
|---|---|---|---|---|
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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | 1-3 h | 45-90 min | 30-60 min | 1-4 Wochen |
Participantsdifferent | 1-5 | 4-12 | 3-12 | 1-6 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions | Experiment results, Decision log, Learning summary |
Tagsno overlap | AnalyticsConversionGrowth | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection | ExperimentsGrowthAnalyticsValidation |



