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 | ![]() Operations Scatter Diagram | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model |
|---|---|---|---|---|
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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–90 min | 30-90 min | 15-45 min | 1-4 h |
Participantsdifferent | 3-10 | 1-4 | 1-3 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Scatter Plot, Korrelationsnotiz, Hypothesenliste | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | SynthesisQualitativeRoot cause | Root causeQualityVisualization | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |



