View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Business Strategy Scenario Planning |  UX Research HEART Framework |  Product Strategy KPI Tree |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 Tage | 0.5-2 Tage | 120 min initial, dann laufend | 90-180 min initial, dann laufend |
Participantsdifferent | 10-50 | 4-12 | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Scenario Set, Strategic Implications, Robust Options | HEART-GSM Table, Dashboard | KPI Tree, Owner List |
Tagsno overlap | SatisfactionPrioritizationCustomer | StrategyUncertaintyPlanning | MetricsUX researchMeasurementSatisfaction | MetricsStrategyAlignmentMeasurement |