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 C4 Model |  Architecture Request for Comments |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 45–90 min | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 3-10 | 1-5 | 3-20 Reviewer |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | Context Diagram, Container Diagram, Component Diagram | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | ArchitectureCommunicationVisualization | ArchitectureDecisionAsyncGovernance |