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 | ![]() Facilitation Consensus Workshop | ![]() Facilitation Responsibility Poker |
|---|---|---|---|
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 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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 2-4 h | 1-3 h | 45-90 min |
Participantsdifferent | 5-15 | 5-30 | 3-10 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Consensus Clusters, Theme Titles, Priority Areas | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | RequirementsArchitectureWorkshop | FacilitationConsensusWorkshopAlignment | RolesResponsibilityTeamFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






