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 |  Product Strategy RICE Scoring |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 1-4 h | 30-60 min | 60-90 min | 90-180 min |
Participantsdifferent | 1-5 | 2-8 | 2-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ICE Table, Top Idea List | RICE Scores, Ranked List, Assumption Log | CoD Table, Prioritization Sequence |
Tagsno overlap | ArchitectureCommunicationVisualization | PrioritizationScoringGrowthDecision | PrioritizationScoringRoadmapTradeoffs | PrioritizationDeliveryEconomicsDecision |