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 | ![]() Domain Modeling Domain Context Map | ![]() Business Strategy Balanced Scorecard | ![]() Product Strategy Counter Metrics |
|---|---|---|---|---|
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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-2 h | 1-3 h | Halber Tag bis mehrere Wochen | 30-60 min |
Participantsdifferent | 1-8 | 3-10 | 4-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Domain Context Map, Boundary Notes, Ownership Map | Balanced Scorecard, Strategic Measures, Initiative Map | Counter Metric List, Guardrail Definitions |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignContextBoundaries | StrategyMetricsExecution | MetricsMeasurementStrategyExperiments |



