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) |  UX Design Service Blueprinting |  Operations 5 Whys |
|---|---|---|---|
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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | High | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 0.5-2 Tage | 15-30 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 6-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Service Blueprint, Fail Points, Ownership Map | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Service designOperationsJourneyBlueprint | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
