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 Personas |  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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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 | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 Tage | 1-4 h | 1-2 Tage |
Participantsdifferent | 3-10 | Internes Team | 1-5 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Persona Profiles, Needs Summary, Scenario Notes | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | JourneyCustomerService designCanvas | ResearchCustomerSynthesis | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |