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 |  Innovation Design Thinking |  Architecture Risk Storming |
|---|---|---|---|---|
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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 Tage | 2-4 h | 1 Tag bis mehrere Wochen | 60-90 min |
Participantsdifferent | Internes Team | 5-15 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Quality Scenarios, Priority List, Architecture Concerns | Problem Statement, Prototype, Test Learnings | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ResearchCustomerSynthesis | RequirementsArchitectureWorkshop | InnovationPrototypeResearch | RiskArchitectureWorkshopValidation |