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)Team Topologies Interaction ModesExpectation Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Team Design Team Topologies Interaction Modes |  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 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. | 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 |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Half day | 45-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Workshop + async | Workshop | 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 | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
