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 Decision Record |  Architecture C4 Model |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 15-45 min | 1-4 h | 60-120 min |
Participantsdifferent | Internes Team | 1-3 | 1-5 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |