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 Funnel Analysis | ![]() Delivery RAID Log | ![]() Growth A/B Testing |
|---|---|---|---|---|
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. | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium | Low | High |
Timedifferent | 15-45 min | 1-3 h | 30 min Setup, dann laufend | 1-4 Wochen |
Participantsdifferent | 1-3 | 1-5 | 1-3 maintaining, briefing for everyone | 1-6 |
Formatsame | Async | Async | Async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Funnel report, Drop-off analysis, Optimization hypotheses | RAID Log, Status Report Source | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AnalyticsConversionGrowth | RiskTrackingStakeholdersGovernance | ExperimentsGrowthAnalyticsValidation |



