View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Strategy RICE Scoring |  Product Strategy ICE Scoring |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 30-60 min |
Participantsdifferent | 1-5 | Designers, developers as users, and facilitation | 2-10 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RICE Scores, Ranked List, Assumption Log | ICE Table, Top Idea List |
Tagsno overlap | PrioritizationOperationsPortfolio | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationScoringRoadmapTradeoffs | PrioritizationScoringGrowthDecision |