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 Pirate Metrics AARRR |  Architecture arc42 |  Architecture Architecture Decision Record |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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-2 h Setup, laufend | 1-2 Tage | 15-45 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-4 | 1-3 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | AARRR funnel, Metric baseline, Experiment backlog | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Experiment results, Decision log, Learning summary |
Tagsno overlap | GrowthMetricsExperiments | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ExperimentsGrowthAnalyticsValidation |