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 Views and Beyond |  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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-3 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-4 | 1-4 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Architecture Views, Cross-view Notes, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ValidationDemandMVP | DocumentationStakeholdersArchitecture | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
