View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Service Blueprinting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture arc42 |
|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | High | High | Low |
Timedifferent | 0.5-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage |
Participantsdifferent | 6-12 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDocumentationCommunication |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
