View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making DACI |  Facilitation Expectation Mapping |  Delivery RAID Log |
|---|---|---|---|---|
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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 45-90 min | 30 min Setup, dann laufend |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-10 | 3-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | DACI Matrix, Decision Owner, Decision Log | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | DecisionRolesGovernanceAlignment | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance |