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 ARID (Active Reviews for Intermediate Designs) |  Operations ABC Analysis |  Product Strategy ICE Scoring |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 30-60 min | 1-4 Wochen |
Participantsdifferent | Designers, developers as users, and facilitation | 1-5 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ABC Classification, Focus Rules, Control List | ICE Table, Top Idea List | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationOperationsPortfolio | PrioritizationScoringGrowthDecision | ExperimentsGrowthAnalyticsValidation |