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 ABC Analysis |  UX Research Tree Testing |  Operations After-Action 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. | 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. | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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 | Low | Medium | Low |
Timedifferent | 1-2 Tage | 30-60 min | 1-2 Tage | 20-45 min |
Participantsdifferent | 10-50 | 1-5 | Based on research question | 3-12 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Findability Metrics, Path Analysis, Revised IA | Lessons learned, Action items, Event summary |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | Information architectureNavigationFindability | LearningOperationsImprovement |