View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Spotify Model MappingStakeholder MappingExpectation Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Team Design Spotify Model Mapping |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min | 60–90 min | 45-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-15 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |