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 DACI |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | Stunden bis wenige Tage | 30-60 min | 1-2 Tage |
Participantsdifferent | 1-3 | 1-4 | 2-10 | 1-4 |
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 | DACI Matrix, Decision Owner, Decision Log | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationDemandMVP | DecisionRolesGovernanceAlignment | ArchitectureDocumentationCommunication |