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 arc42 | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 1-2 Tage | 15-45 min | 1-4 h |
Participantsdifferent | 2-8 | 1-4 | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |



