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 |  Product Discovery Jobs to Be Done |  Innovation Design Thinking |  UX Research Personas |
|---|---|---|---|---|
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 2-4 h | 1-3 Wochen | 1 Tag bis mehrere Wochen | 1-3 Tage |
Participantsdifferent | 5-15 | 5-12 Interviews | 4-10 | Internes Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Job Stories, Outcome Statements, Opportunity List | Problem Statement, Prototype, Test Learnings | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | RequirementsArchitectureWorkshop | CustomerOutcomesNeeds | InnovationPrototypeResearch | ResearchCustomerSynthesis |