View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Team Design Team API |
|---|---|---|---|
Purposedifferent | 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. | 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. |
Complexitydifferent | Low | High | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | Half day initial, dann laufend |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Team API Document |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCommunicationService |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
