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 |  Product Discovery Outcome-Driven Innovation |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | 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 | 2-4 h | 1-3 Tage | Mehrere Wochen | 60-90 min |
Participantsdifferent | 5-15 | Internes Team | 2-6 researchers plus sample | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Persona Profiles, Needs Summary, Scenario Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RequirementsArchitectureWorkshop | ResearchCustomerSynthesis | OutcomesInnovationResearchQuantitative | RiskArchitectureWorkshopValidation |