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 |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |  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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | 60–90 min | 1-2 h | 60-120 min |
Participantsdifferent | Internes Team | 2-8 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ResearchCustomerSynthesis | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |