View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Personas |  Business Strategy Balanced Scorecard |  UX Research HEART Framework |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. | 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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 Tage | Halber Tag bis mehrere Wochen | 120 min initial, dann laufend | 1-2 Tage |
Participantsdifferent | Internes Team | 4-12 | 3-6 | 10-50 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Balanced Scorecard, Strategic Measures, Initiative Map | HEART-GSM Table, Dashboard | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | ResearchCustomerSynthesis | StrategyMetricsExecution | MetricsUX researchMeasurementSatisfaction | SatisfactionPrioritizationCustomer |