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 Personas |  Architecture Architecture Communication Canvas |  UX Design Customer Journey Canvas |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Tage | 60-120 min | 1-3 h | 1-4 h |
Participantsdifferent | Internes Team | 2-8 | 3-10 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Customer Journey Canvas, Pain Points, Experience Opportunities | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureCommunicationStakeholdersCanvas | JourneyCustomerService designCanvas | ArchitectureCommunicationVisualization |