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 |  Domain Modeling Context Map |  Engineering Goal Question Metric |  Product Strategy KPI Tree |
|---|---|---|---|---|
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. | 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. | 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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 90-180 min | 90-180 min initial, dann laufend |
Participantsdifferent | 3-12 | 2-8 | 3-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Context Map, Integration Patterns, Boundary Notes | GQM Table, Metric Profiles | KPI Tree, Owner List |
Tagsno overlap | KnowledgeMappingRisk | Domain-Driven DesignBoundariesStrategy | MetricsMeasurementEngineeringAlignment | MetricsStrategyAlignmentMeasurement |