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 |  Decision Making DACI |
|---|---|---|---|---|
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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | Stunden bis wenige Tage | 1-3 h | 30-60 min |
Participantsdifferent | 1-3 | 1-4 | 1-8 | 2-10 |
Formatdifferent | Async | Workshop + 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 | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationDemandMVP | SensemakingDecisionRationale | DecisionRolesGovernanceAlignment |