View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Strategy ICE Scoring | ![]() Architecture Request for Comments | ![]() Architecture Architecture Decision Record | ![]() Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 30-60 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-3 | 2-10 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernanceAlignment |



