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 Responsibility Poker |  Facilitation Expectation Mapping |  Facilitation Consensus Workshop |
|---|---|---|---|---|
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 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 45-90 min | 45-90 min | 1-3 h |
Participantsdifferent | 5-15 | 3-10 | 3-12 | 5-30 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Responsibility Map, Role Agreements, Open Questions | Expectation Map, Alignment Notes, Agreements | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | RequirementsArchitectureWorkshop | RolesResponsibilityTeamFacilitation | AlignmentStakeholdersTeam | FacilitationConsensusWorkshopAlignment |