View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() Growth A/B Testing | ![]() Growth Pirate Metrics AARRR | ![]() Product Discovery Smoke Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 1-2 Tage | 1-4 Wochen | 1-2 h Setup, laufend | 1-5 Tage |
Participantsdifferent | 1-4 | 1-6 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Experiment results, Decision log, Learning summary | AARRR funnel, Metric baseline, Experiment backlog | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ArchitectureDocumentationCommunication | ExperimentsGrowthAnalyticsValidation | GrowthMetricsExperiments | ValidationExperimentsDemandGrowth |



