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 | ![]() Knowledge Modeling Concept Mapping | ![]() Knowledge Modeling IBIS | ![]() UX Design Customer Journey Canvas |
|---|---|---|---|---|
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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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 | High | Medium | Medium | Medium |
Timedifferent | 0.5-2 Tage | 1-2 h | 1-3 h | 1-3 h |
Participantsdifferent | 6-12 | 1-8 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Concept Map, Relationship Labels, Knowledge Gaps | Issue Map, Positions, Argument Notes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | Service designOperationsJourneyBlueprint | KnowledgeConceptsMappingSensemaking | RationaleKnowledgeDecision | JourneyCustomerService designCanvas |



