View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Growth Pirate Metrics AARRR |  UX Research HEART Framework |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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 | Medium | Medium | High |
Timedifferent | 1-3 h | 1-2 h Setup, laufend | 120 min initial, dann laufend | 1-4 Wochen |
Participantsdifferent | 3-8 | 2-8 | 3-6 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | AARRR funnel, Metric baseline, Experiment backlog | HEART-GSM Table, Dashboard | Experiment results, Decision log, Learning summary |
Tagsno overlap | FlowMeasurementConstraints | GrowthMetricsExperiments | MetricsUX researchMeasurementSatisfaction | ExperimentsGrowthAnalyticsValidation |