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 |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |