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 Knowledge Mapping |  Business Strategy Balanced Scorecard |  Domain Modeling Context Map |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium |
Timedifferent | 1-3 h | Halber Tag bis mehrere Wochen | 1-3 h | 1-2 h |
Participantsdifferent | 3-12 | 4-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Balanced Scorecard, Strategic Measures, Initiative Map | Context Map, Integration Patterns, Boundary Notes | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | StrategyMetricsExecution | Domain-Driven DesignBoundariesStrategy | KnowledgeConceptsMappingSensemaking |