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 |  Decision Making Argument Mapping |
|---|---|---|---|
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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 15-45 min | Stunden bis wenige Tage | 1-3 h |
Participantsdifferent | 1-3 | 1-4 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationDemandMVP | SensemakingDecisionRationale |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
