View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Responsibility PokerATAM (Architecture Tradeoff Analysis Method)Expectation MappingStakeholder Mapping
| Criterion |  Facilitation Responsibility Poker |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Expectation Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 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 | Low | High | Low | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | 60–90 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Expectation Map, Alignment Notes, Agreements | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersTeam | StakeholdersAlignmentFacilitationChange |