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 Research Affinity Diagramming |  Architecture arc42 |
|---|---|---|---|---|
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 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. | 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 Tage | 60-120 min | 45–90 min | 1-2 Tage |
Participantsdifferent | Internes Team | 2-8 | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Theme clusters, Insight statements, Opportunity areas | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureCommunicationStakeholdersCanvas | SynthesisQualitativeRoot cause | ArchitectureDocumentationCommunication |