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 |  UX Research Affinity Diagramming |  Architecture Risk Storming |  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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | 45–90 min | 60-90 min | 1-2 Tage |
Participantsdifferent | 1-3 | 3-10 | 4-12 | 1-4 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | RiskArchitectureWorkshopValidation | ArchitectureDocumentationCommunication |