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 |  Engineering Goal Question Metric |  Domain Modeling Context Map |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 90-180 min | 1-3 h | Halber Tag bis mehrere Wochen |
Participantsdifferent | 3-12 | 3-6 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | GQM Table, Metric Profiles | Context Map, Integration Patterns, Boundary Notes | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | KnowledgeMappingRisk | MetricsMeasurementEngineeringAlignment | Domain-Driven DesignBoundariesStrategy | StrategyMetricsExecution |