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 Concept Mapping | ![]() UX Design Service Blueprinting | ![]() Operations ALPEN Method | ![]() Operations Getting Things Done |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 h | 0.5-2 Tage | 10-20 min daily | 1-2 h Setup, laufend |
Participantsdifferent | 1-8 | 6-12 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Service Blueprint, Fail Points, Ownership Map | Daily Plan, Time Estimates, Review Notes | Action Lists, Project List, Review Routine |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Service designOperationsJourneyBlueprint | PlanningTime managementProductivityOperations | ProductivityPlanningTasksExecution |



