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 |  Product Strategy RICE Scoring |  Delivery RAID Log |  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 initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 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 | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 2-10 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RICE Scores, Ranked List, Assumption Log | RAID Log, Status Report Source | ICE Table, Top Idea List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | PrioritizationScoringRoadmapTradeoffs | RiskTrackingStakeholdersGovernance | PrioritizationScoringGrowthDecision |