View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Topologies Interaction ModesATAM (Architecture Tradeoff Analysis Method)Expectation Mapping
| Criterion |  Team Design Team Topologies Interaction Modes |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | Half day | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | 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 |
Tagsno overlap | TeamAlignmentCollaborationOrganization | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
