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 | ![]() UX Design Customer Journey 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. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30–60 min | 1-3 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 | Customer Journey Canvas, Pain Points, Experience Opportunities | Architecture Document, Context View, Runtime View, Deployment View | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | SynthesisQualitativeWorkshop | JourneyCustomerService designCanvas | ArchitectureDocumentationCommunication | SynthesisQualitativeRoot cause |



