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 Software Architecture Canvas |  Architecture Architecture Decision Record |  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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. | 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 | 45–90 min | 1-2 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-10 | 3-10 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Architecture Canvas, Goals, Constraints, Quality Attributes | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | SynthesisQualitativeRoot cause | CanvasArchitectureAlignmentWorkshop | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |