View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingATAM (Architecture Tradeoff Analysis Method)Barrier AnalysisFailure Mode and Effects Analysis
| Criterion |  Facilitation Expectation Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Barrier Analysis |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | High | Medium | High |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 2-6 h |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 2-6 | 3-10 |
Formatdifferent | Workshop | Workshop + async | 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 | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | Root causeSafetyIncident | RiskQualityOperationsRoot cause |