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