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 |  UX Research Personas |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|---|
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. | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 2-4 h | 1-3 Wochen | 1-3 Tage | Mehrere Wochen |
Participantsdifferent | 5-15 | 5-12 Interviews | Internes Team | 2-6 researchers plus sample |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Job Stories, Outcome Statements, Opportunity List | Persona Profiles, Needs Summary, Scenario Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | RequirementsArchitectureWorkshop | CustomerOutcomesNeeds | ResearchCustomerSynthesis | OutcomesInnovationResearchQuantitative |