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 ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |
|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 h Setup, laufend | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | AARRR funnel, Metric baseline, Experiment backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | GrowthMetricsExperiments | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
