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 ARID (Active Reviews for Intermediate Designs) |  Operations Change Analysis |  Growth A/B Testing |
|---|---|---|---|---|
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. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 | Low | Medium | Medium | High |
Timedifferent | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional | 45-120 min | 1-4 Wochen |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 2-6 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | ICE Table, Top Idea List | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Experiment results, Decision log, Learning summary |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureEngineeringFeedbackValidationTasks | ChangeRoot causeTroubleshootingComparison | ExperimentsGrowthAnalyticsValidation |