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 |  Operations ALPEN Method |  Product Discovery Jobs to Be Done |  Operations Getting Things Done |
|---|---|---|---|---|
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. | 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. | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 10-20 min daily | 1-3 Wochen | 1-2 h Setup, laufend |
Participantsdifferent | 10-50 | 1 | 5-12 Interviews | 1 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Daily Plan, Time Estimates, Review Notes | Job Stories, Outcome Statements, Opportunity List | Action Lists, Project List, Review Routine |
Tagsno overlap | SatisfactionPrioritizationCustomer | PlanningTime managementProductivityOperations | CustomerOutcomesNeeds | ProductivityPlanningTasksExecution |