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 Feynman Technique |  Product Strategy KPI Tree |  Engineering Goal Question Metric |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. | 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 people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-60 min | 90-180 min initial, dann laufend | 90-180 min | 1-2 h |
Participantsdifferent | 1 | 3-8 | 3-6 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | KPI Tree, Owner List | GQM Table, Metric Profiles | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | LearningKnowledgeUnderstanding | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment | AlignmentStakeholdersStrategyFacilitation |