View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Affinity Diagramming |  Architecture Architecture Decision Record |  Operations Root Cause Tree Analysis |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45–90 min | 15-45 min | 1-3 h | 1-2 Tage |
Participantsdifferent | 3-10 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale | Cause Tree, Evidence Notes, Countermeasures | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance | Root causeTreeIncidentQuality | ArchitectureDocumentationCommunication |