View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:PretotypingARID (Active Reviews for Intermediate Designs)Hypothesis-Driven TroubleshootingLean Startup
| Criterion |  Product Discovery Pretotyping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Engineering Hypothesis-Driven Troubleshooting |  Innovation Lean Startup |
|---|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 2–4 h review as a planning range; preparation and evaluation additional | 30-240 min | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | Designers, developers as users, and facilitation | 1-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
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 | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | ArchitectureEngineeringFeedbackValidationTasks | TroubleshootingProblem solvingDiagnosis | LeanStartupValidationMVP |