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 |  UX Research User Interviews |  Operations Getting Things Done |  Operations ALPEN Method |
|---|---|---|---|---|
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. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 Tage | 30–60 min per interview | 1-2 h Setup, laufend | 10-20 min daily |
Participantsdifferent | 10-50 | 1 participant per interview | 1 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Interview Notes, Themes, Insight Summary | Action Lists, Project List, Review Routine | Daily Plan, Time Estimates, Review Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | QualitativeResearchCustomerDiscovery | ProductivityPlanningTasksExecution | PlanningTime managementProductivityOperations |