View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:PretotypingSAAM (Software Architecture Analysis Method)Lean StartupARID (Active Reviews for Intermediate Designs)
| Criterion |  Product Discovery Pretotyping |  Architecture SAAM (Software Architecture Analysis Method) |  Innovation Lean Startup |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | Preparation, scenario analysis, and findings review; effort depends on scope | Wochen bis Monate je Lernzyklus | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-4 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ValidationDemandMVP | ArchitectureChangeAnalysisComparisonQuality | LeanStartupValidationMVP | ArchitectureEngineeringFeedbackValidationTasks |