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 RICE Scoring |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |  Decision Making Eisenhower Matrix |
|---|---|---|---|---|
Purposedifferent | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 15-30 min |
Participantsdifferent | 2-10 | Designers, developers as users, and facilitation | 4-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RICE Scores, Ranked List, Assumption Log | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog | Eisenhower Matrix, Action List, Delegation Notes |
Tagsno overlap | PrioritizationScoringRoadmapTradeoffs | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation | PrioritizationFocusTasks |