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 |  Architecture arc42 |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 1-2 Tage | 1-2 h Setup, laufend | 1-4 Wochen |
Participantsdifferent | 3-6 | 1-4 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | HEART-GSM Table, Dashboard | Architecture Document, Context View, Runtime View, Deployment View | AARRR funnel, Metric baseline, Experiment backlog | Experiment results, Decision log, Learning summary |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | ArchitectureDocumentationCommunication | GrowthMetricsExperiments | ExperimentsGrowthAnalyticsValidation |