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 Design Customer Journey Canvas |  UX Research Affinity Diagramming |  Architecture C4 Model |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45–90 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 3-10 | 3-10 | 1-5 | 1-4 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Theme clusters, Insight statements, Opportunity areas | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | JourneyCustomerService designCanvas | SynthesisQualitativeRoot cause | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |