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 Views and Beyond | ![]() Architecture C4 Model | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–90 min | 1-3 Tage | 1-4 h | 15-45 min |
Participantsdifferent | 3-10 | 1-4 | 1-5 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Architecture Views, Cross-view Notes, Rationale | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | SynthesisQualitativeRoot cause | DocumentationStakeholdersArchitecture | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |



