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 |  Agile WSJF |  Product Strategy RICE Scoring |  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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 | High | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 60-90 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 2-10 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Ranked Backlog, Cost-of-Delay Assumptions | RICE Scores, Ranked List, Assumption Log | ICE Table, Top Idea List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | LeanEconomicsSequencePrioritization | PrioritizationScoringRoadmapTradeoffs | PrioritizationScoringGrowthDecision |