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)Team Topologies Interaction Modes
| Criterion |  Team Design Spotify Model Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|
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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope | Half day |
Participantsdifferent | 5-15 | Evaluation team, architects, and relevant stakeholders | Team-Leads plus Architecture |
Formatdifferent | Workshop | 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 | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCollaborationOrganization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
