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 Design Service Blueprinting |  Operations After-Action Review |  Operations ABC Analysis |
|---|---|---|---|---|
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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-2 Tage | 0.5-2 Tage | 20-45 min | 30-60 min |
Participantsdifferent | 10-50 | 6-12 | 3-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Service Blueprint, Fail Points, Ownership Map | Lessons learned, Action items, Event summary | ABC Classification, Focus Rules, Control List |
Tagsno overlap | SatisfactionPrioritizationCustomer | Service designOperationsJourneyBlueprint | LearningOperationsImprovement | PrioritizationOperationsPortfolio |