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 Expectation Mapping |  Facilitation Consensus Workshop |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 45-90 min | 1-3 h | 60–90 min |
Participantsdifferent | 5-15 | 3-12 | 5-30 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Expectation Map, Alignment Notes, Agreements | Consensus Clusters, Theme Titles, Priority Areas | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RequirementsArchitectureWorkshop | AlignmentStakeholdersTeam | FacilitationConsensusWorkshopAlignment | StakeholdersAlignmentFacilitationChange |