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 Architecture Decision Record |  Product Discovery Pretotyping |  Product Discovery Assumption Mapping |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | Stunden bis wenige Tage | 45-60 min | 60-90 min |
Participantsdifferent | 1-3 | 1-4 | 2-8 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationDemandMVP | AssumptionsRiskExperimentsValidation | RiskArchitectureWorkshopValidation |