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 |  Decision Making Force Field Analysis |
|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 20-60 min | 90-180 min initial, dann laufend | 45-90 min |
Participantsdifferent | 1 | 3-8 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | KPI Tree, Owner List | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | LearningKnowledgeUnderstanding | MetricsStrategyAlignmentMeasurement | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
