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 Jobs to Be Done |  Operations Process Mapping |  Product Discovery Kano Model |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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 a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 h | 1-2 Tage | 20-45 min |
Participantsdifferent | 5-12 Interviews | 3-10 | 10-50 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Process Map, Handoff List, Improvement Backlog | Kano Matrix, Feature Classes, Priority Themes | Lessons learned, Action items, Event summary |
Tagsno overlap | CustomerOutcomesNeeds | ProcessOperationsImprovement | SatisfactionPrioritizationCustomer | LearningOperationsImprovement |