View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research HEART Framework |  Delivery RAID Log |  Growth Pirate Metrics AARRR |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Medium | High |
Timedifferent | 120 min initial, dann laufend | 30 min Setup, dann laufend | 1-2 h Setup, laufend | 1-4 Wochen |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | HEART-GSM Table, Dashboard | RAID Log, Status Report Source | AARRR funnel, Metric baseline, Experiment backlog | Experiment results, Decision log, Learning summary |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | RiskTrackingStakeholdersGovernance | GrowthMetricsExperiments | ExperimentsGrowthAnalyticsValidation |