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 arc42 |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | High | Low | Low |
Timedifferent | 0.5-2 Tage | 1-2 Tage | 60–90 min |
Participantsdifferent | 6-12 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
