View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fishbone DiagramService BlueprintingArchitecture Communication CanvasCustomer Journey Canvas
| Criterion |  Operations Fishbone Diagram |  UX Design Service Blueprinting |  Architecture Architecture Communication Canvas |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30-60 min | 0.5-2 Tage | 60-120 min | 1-3 h |
Participantsdifferent | 2-8 | 6-12 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Service Blueprint, Fail Points, Ownership Map | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | Root causeQualityOperations | Service designOperationsJourneyBlueprint | ArchitectureCommunicationStakeholdersCanvas | JourneyCustomerService designCanvas |