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 C4 Model |  Decision Making DACI |  Architecture Request for Comments |
|---|---|---|---|---|
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 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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 | 45–90 min | 1-4 h | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-10 | 1-5 | 2-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Context Diagram, Container Diagram, Component Diagram | DACI Matrix, Decision Owner, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureCommunicationVisualization | DecisionRolesGovernanceAlignment | ArchitectureDecisionAsyncGovernance |