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 Decision Rights Mapping |  Product Strategy ICE Scoring |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 30-60 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 2-8 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | ICE Table, Top Idea List | CoD Table, Prioritization Sequence |
Tags1 shared | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | PrioritizationScoringGrowthDecision | PrioritizationDeliveryEconomicsDecision |