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 Empathy Mapping |  Architecture Software Architecture Canvas |  Architecture arc42 |  UX Research Affinity Diagramming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–60 min | 1-2 h | 1-2 Tage | 45–90 min |
Participantsdifferent | 4-8 | 3-10 | 1-4 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Architecture Canvas, Goals, Constraints, Quality Attributes | Architecture Document, Context View, Runtime View, Deployment View | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | SynthesisQualitativeWorkshop | CanvasArchitectureAlignmentWorkshop | ArchitectureDocumentationCommunication | SynthesisQualitativeRoot cause |