View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Customer Journey CanvasATAM (Architecture Tradeoff Analysis Method)Fishbone DiagramArchitecture Communication Canvas
| Criterion | ![]() UX Design Customer Journey Canvas | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations Fishbone Diagram | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 60-120 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Fishbone Diagram, Cause Categories, Investigation Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | JourneyCustomerService designCanvas | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations | ArchitectureCommunicationStakeholdersCanvas |



