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 Customer Journey Mapping |  Operations Getting Things Done |  Operations Weekly Review |
|---|---|---|---|---|
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 a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 2-4 h | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | 10-50 | 4-10 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Journey Map, Pain-point List, Opportunity Backlog | Action Lists, Project List, Review Routine | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyServiceService design | ProductivityPlanningTasksExecution | ProductivityExecutionPlanning |