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 ICE Scoring | ![]() Delivery RAID Log | ![]() Decision Making Risk Matrix |
|---|---|---|---|---|
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 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, 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-3 maintaining, briefing for everyone | 3-10 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ICE Table, Top Idea List | RAID Log, Status Report Source | Risk Matrix, Top Risk List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | PrioritizationScoringGrowthDecision | RiskTrackingStakeholdersGovernance | RiskDecisionPrioritizationAssessment |



