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 | ![]() Facilitation Consensus Workshop | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|---|
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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 1-3 Tage | 1-3 h | 1-2 h |
Participantsdifferent | 5-15 | Internes Team | 5-30 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Persona Profiles, Needs Summary, Scenario Notes | Consensus Clusters, Theme Titles, Priority Areas | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RequirementsArchitectureWorkshop | ResearchCustomerSynthesis | FacilitationConsensusWorkshopAlignment | CanvasArchitectureAlignmentWorkshop |



