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 Architecture Decision Record |  Growth Pirate Metrics AARRR |  Product Discovery Assumption Mapping |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 1-2 h Setup, laufend | 45-60 min | 60-90 min |
Participantsdifferent | 1-3 | 2-8 | 2-8 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | AARRR funnel, Metric baseline, Experiment backlog | Assumption map, Test backlog, Risk ranking | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | GrowthMetricsExperiments | AssumptionsRiskExperimentsValidation | RiskArchitectureWorkshopValidation |