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 C4 Model |  Architecture Request for Comments |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-60 min | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 1-5 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | ICE Table, Top Idea List | Context Diagram, Container Diagram, Component Diagram | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureCommunicationVisualization | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
