View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making DACI | ![]() UX Research Affinity Diagramming | ![]() Architecture arc42 | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 45–90 min | 1-2 Tage | 15-45 min |
Participantsdifferent | 2-10 | 3-10 | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | DACI Matrix, Decision Owner, Decision Log | Theme clusters, Insight statements, Opportunity areas | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | DecisionRolesGovernanceAlignment | SynthesisQualitativeRoot cause | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |



