View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Service BlueprintingArchitecture Decision RecordFailure Mode and Effects AnalysisFishbone Diagram
| Criterion |  UX Design Service Blueprinting |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | 0.5-2 Tage | 15-45 min | 2-6 h | 30-60 min |
Participantsdifferent | 6-12 | 1-3 | 3-10 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | Root causeQualityOperations |