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 C4 Model |  Product Strategy ICE Scoring |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Low | Medium |
Timedifferent | 1-4 h | 30-60 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-5 | 2-8 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ICE Table, Top Idea List | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureCommunicationVisualization | PrioritizationScoringGrowthDecision | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |