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 MappingRoot Cause Tree AnalysisATAM (Architecture Tradeoff Analysis Method)5 Whys
| Criterion |  Facilitation Expectation Mapping |  Operations Root Cause Tree Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45-90 min | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min |
Participantsdifferent | 3-12 | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Cause Tree, Evidence Notes, Countermeasures | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Root cause notes, Countermeasures |
Tagsno overlap | AlignmentStakeholdersTeam | Root causeTreeIncidentQuality | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving |