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 Request for Comments |  Decision Making Risk Matrix |  Growth A/B Testing |  Product Strategy ICE Scoring |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 1-4 Wochen | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 1-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk Matrix, Top Risk List | Experiment results, Decision log, Learning summary | ICE Table, Top Idea List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskDecisionPrioritizationAssessment | ExperimentsGrowthAnalyticsValidation | PrioritizationScoringGrowthDecision |