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 | ![]() UX Research Affinity Diagramming | ![]() Architecture Software Architecture Canvas | ![]() UX Research Empathy 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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 0.5-2 Tage | 45–90 min | 1-2 h | 30–60 min |
Participantsdifferent | 6-12 | 3-10 | 3-10 | 4-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Theme clusters, Insight statements, Opportunity areas | Architecture Canvas, Goals, Constraints, Quality Attributes | Empathy Map, Assumptions List, Research Gaps |
Tagsno overlap | Service designOperationsJourneyBlueprint | SynthesisQualitativeRoot cause | CanvasArchitectureAlignmentWorkshop | SynthesisQualitativeWorkshop |



