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 RICE Scoring | ![]() Architecture C4 Model | ![]() Architecture Architecture Decision Record | ![]() Product Strategy ICE Scoring |
|---|---|---|---|---|
Purposedifferent | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Low | Low | Low |
Timedifferent | 60-90 min | 1-4 h | 15-45 min | 30-60 min |
Participantsdifferent | 2-10 | 1-5 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | RICE Scores, Ranked List, Assumption Log | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | ICE Table, Top Idea List |
Tagsno overlap | PrioritizationScoringRoadmapTradeoffs | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | PrioritizationScoringGrowthDecision |



