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) |  Business Strategy Value Chain Analysis |  Product Strategy DIBB |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Half day | 1-2 h | 45-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Value Chain Map, Lever List | DIBB document, Belief list, Bet list, Learning report | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyBusiness modelDiagnosisAnalysis | StrategyDecisionAssumptionsHypothesis | AssumptionsRiskExperimentsValidation |