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 Quality Attribute Workshop | ![]() UX Research Empathy Mapping | ![]() Architecture Software Architecture 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Tage | 2-4 h | 30–60 min | 1-2 h |
Participantsdifferent | Internes Team | 5-15 | 4-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Quality Scenarios, Priority List, Architecture Concerns | Empathy Map, Assumptions List, Research Gaps | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ResearchCustomerSynthesis | RequirementsArchitectureWorkshop | SynthesisQualitativeWorkshop | CanvasArchitectureAlignmentWorkshop |



