View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Design Service Blueprinting |
|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitydifferent | Low | High | High |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 0.5-2 Tage |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 6-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | 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 |
Tagsno overlap | Root causeQualityOperations | ArchitectureQualityRiskTradeoffsStakeholders | Service designOperationsJourneyBlueprint |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
