View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() UX Design Service Blueprinting | ![]() Knowledge Modeling Concept Mapping |
|---|---|---|---|
Purposedifferent | 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 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | 0.5-2 Tage | 1-2 h |
Participantsdifferent | 2-8 | 6-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Service Blueprint, Fail Points, Ownership Map | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | RationaleKnowledgeDecision | Service designOperationsJourneyBlueprint | KnowledgeConceptsMappingSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






