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 Request for Comments |  Architecture Software Architecture Canvas |  UX Research Affinity Diagramming |  UX Research Empathy Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 45–90 min | 30–60 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 3-10 | 4-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Canvas, Goals, Constraints, Quality Attributes | Theme clusters, Insight statements, Opportunity areas | Empathy Map, Assumptions List, Research Gaps |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CanvasArchitectureAlignmentWorkshop | SynthesisQualitativeRoot cause | SynthesisQualitativeWorkshop |