View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Argument Mapping | ![]() Architecture C4 Model | ![]() UX Research Affinity Diagramming | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-4 h | 45–90 min | 15-45 min |
Participantsdifferent | 1-8 | 1-5 | 3-10 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Context Diagram, Container Diagram, Component Diagram | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale |
Tagsno overlap | SensemakingDecisionRationale | ArchitectureCommunicationVisualization | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance |



