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 |  UX Design Service Blueprinting |  Architecture arc42 |  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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | 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 | High | Low | Low |
Timedifferent | 1-3 Tage | 0.5-2 Tage | 1-2 Tage | 1-4 h |
Participantsdifferent | Internes Team | 6-12 | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Service Blueprint, Fail Points, Ownership Map | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ResearchCustomerSynthesis | Service designOperationsJourneyBlueprint | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |