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)Business Model Stress TestExpectation Mapping
| Criterion |  Team Design Spotify Model Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Business Strategy Business Model Stress Test |  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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Low |
Timedifferent | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope | Half day | 45-90 min |
Participantsdifferent | 5-15 | Evaluation team, architects, and relevant stakeholders | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | 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 | Stress Test Report, Action Plan per Scenario | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders | StrategyBusiness modelRiskDiagnosis | AlignmentStakeholdersTeam |