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 Discovery Pretotyping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Business Strategy Value Chain Analysis |
|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | Stunden bis wenige Tage | 2–4 h review as a planning range; preparation and evaluation additional | Half day |
Participantsdifferent | 1-4 | Designers, developers as users, and facilitation | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Value Chain Map, Lever List |
Tagsno overlap | ValidationDemandMVP | ArchitectureEngineeringFeedbackValidationTasks | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
