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) |  Facilitation Team Charter |
|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
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 Charter, Working Norms, Role Notes |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCollaboration |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
