View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  UX Research Personas |  Domain Modeling EventStorming |  UX Research Empathy Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 1-3 Tage | 2-8 h | 30–60 min |
Participantsdifferent | 5-15 | Internes Team | 5-12 | 4-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Persona Profiles, Needs Summary, Scenario Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Empathy Map, Assumptions List, Research Gaps |
Tagsno overlap | RequirementsArchitectureWorkshop | ResearchCustomerSynthesis | Domain-Driven DesignEventsDiscoveryWorkshop | SynthesisQualitativeWorkshop |